Ya say Ya want a flowchart o vegastrike

[wirser]

So do want to see how Vegastrike works?
I mean in a visable flowchart?
Here is how
first you need to get both valgrind @
http://www.valgrind.org/
and kcachegrind @
http://kcachegrind.sourceforge.net
build valgrind then kcachegrind
then in ./vegastrike

Code: Select all

callgrind --dump-instr=yes --trace-jump=yes ./vegastrike 

which should pruduce "callgrind.out.XXXX" where x=pid number for the program at the time
and may have more than one part

this is not for the impatient however it will take over an hour just to get to the first place where you can quit the progarm on amd 64 3800
but if you survive the files produced will show you how vegastrike does what it does
all run have to do is run kcachegrind on them and you'll see what I mean

Have fun
ADDED
heres is a screenshot too
look at bottom left on top of toolbar that is 111 BILLION instructions to create so do the math

[ace123]

We once made a Dotty-based inheritance chart using Doxygen... I can't seem to dig it up now but I'll look around for it.

I remember trying it more recently, but my computer ran out of RAM when generating it, so I gave up.


Yeah, there are a lot of memory leaks... but many of them are really hard to fix.

[wirser]

a lot of the leaks reported are someone elses that and it doesn't like 4 bit structures
but stillthere is a lot of debugging data
if you can stand to wait and wait ......

but then I'm just a kid with a new toy rightnow
SO THERE

I remember trying it more recently, but my computer ran out of RAM when generating it, so I gave up.

the bad thing with my box is that it doesn't use smp processors -only one 2 gig ram
all I can say is that it worked the callgrind output files in a bz2 archive at 1.2mb
but this is too big for forum
otherwise I'd share

[ace123]

I copied some of the more notable ones over...
http://vegastrike.sourceforge.net/users ... en_graphs/

"everything.png" actually looks pretty impressive zoomed out too :-p

[wirser]

"everything.png" actually looks pretty impressive zoomed out too :-p

confusing if you follow some of the paths too
although I'm having flashbacks to distant jumpmaps I made
I think I can include it now
open the first part with kcachegrind and you'll see what I mean (without the looonnnggg runtime)

so what did you do to make this amazzing graphics?

[ace123]

Doxygen:
http://www.stack.nl/~dimitri/doxygen/

It's a source code documenter... It works better on smaller and also on well-documented projects.

But it makes nice pretty graphs showing what Classes each other class depends on/uses/inherits.

I think it makes nice graphs for include files, too...

[wirser]

sooo much to learn so little time

your way is more of a static way of generating documentation
the callgrind / valgrind /kcache is based on the dynamic running

both should resonably agree with one another

I perfer the dynamic approach for what I tend to be interested in
esp troubleshooting, but then I'm not writing this stuff either

[targ collective]

You've shown an interest, and that's the first step. You know more about this than I do (admittedly not hard).

I say go for it. Many hands make light work.

[Melonhead]

Are there any equivalents you can recommend for a Win32 environment? Unfortunately, although I've always wanted an excuse to play with Linux, RL considerations are in the way.

[ace123]

This thread has veered a bit off topic.

When you ask for equivalents, what are you talking about exactly? Doxygen works on windows. You can use a profiler on windows (built into VC++).

However, I'm not sure if a Valgrind equivalent works on win32. I suspect that you hope that VC8 just has better memory management checks and can find memory bugs.