On 1/1/07, Andy Dent <[EMAIL PROTECTED]> wrote:
This is a quick sanity check for programming practices - I have
trouble believing I'm unique.
I was challenged recently as to the worth of recording call stacks .
Well, I have been doing some debugging of a drawing program today,
trying to sort out why the Windows version was broken by compiling in
RB200x compared to 5.5.
On three occasions in two hours of debugging, I've wanted to make a
note of a call stack, that's from 4 to 8 levels deep.
If these were things I was noting to fix later, I'd certainly be
recording those stacks as being part of the context of the bug, to
aid further diagnosis. Even when I fix a bug immediately, if it
required much digging I make a point of recording these details in an
issue tracker so I can search for them later if a similar bug occurs.
Maybe my need to do this is a consequence of a programming style that
has highly factored classes, or the nature of the event-driven UI I'm
working on where things like size and rendering code might be called
through very different paths.
Does anyone else out there work or think like this, he asks plaintively?
There are times -- particularly when I'm trying to debug situations
where methods are called by events -- that I really need a good look
at the stack. I find the Stack popup menu is greatly inferior to the
old style (RB 5.5.5 and earlier) Stack list in those situations.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
