on 7/30/02 10:20 PM, Nathan Fisher at virtual1 at pitnet dot net wrote:
>
> I don't mean to keep plugging PC, but well, this is what it's for so...
>
> Reminder: Project Cuisinart does just what Charles is suggesting,
> automatically. I don't think I'd want to try to retro-fit a large
> program that way by hand. ;-)
>
> PC displays the traces in a global floater (which you can hide if you
> like), can save the trace to file as it goes, and indents at each call
> level to increase readability. It's currently the best way available to
> track down failed assertions and hard crashes. If you don't mind taking
> a speed hit, you can make it log every single line in one or all code
> blocks too. It can also be useful if you have a flow-control or
> event-order bug you're trying to nail down.
Ya, great tool. Only problem is that when I use the tracing tool (only), my
program took 1 minutes to load and opening a movie takes another minute.
Navigation takes 30 seconds. Quitting took 2 minutes. The log file was going
at 1 MB every 30-60 second. The program ran 100x slower. You don't want to
hear about extreme mode (never did load, I force quit after 7 minutes) :)
I was able to nail down the method name of a failed assertion (after an hour
of use).
I found that writing out every method to a log file was very very slow so I
modified it so that it puts the last few lines in the clipboard. When the
caps lock is on, it stops logging. So when the dialog pops up, I turn on
caps lock.
It worked almost as fast as normal. I was able to duplicate the failed
assertion again, but when I click quit, it froze (weird huh? I thought Quit
stops the comp from freezing/crashing? I usually Press OK and it never
crashes). I was not able to find out where it happened. The next time I
duplicated it (turned on caps lock), I clicked Ok and it worked fine. So it
gave the same Method name as in the above :)
When I put "'extreme" at start of that method, PC would only process half
way and write out a "block" file. After I removed it, it still would not
work with it :(...Just when I was so close on one.
Regards,
Lo Saeteurn
|