Darren New <dne### [at] sanrrcom> wrote:
> The stack trace in something like Java or Tcl is as useful as a full stack 
> trace from gdb is in C, when you haven't actually clobbered memory in the 
> unsafe languages.  I.e., you walk up the stack until you find your code that 
> invokes the not-your-code, then you figure out what happened from there.

  But that's the problem: The buggy part of your code might not be in the
call stack at all anymore at the time the null pointer exception (or whatever
other symptom) happens.

  I know what a stack trace is and how to read it, and why I mentioned
several times that "the debugger is of no help whatsoever".

-- 
                                                          - Warp

Post a reply to this message