On Wed, 2004-02-18 at 19:49, Eric Pouech wrote: > this would be as intrusive as using the debugger (I assume that the > running process would be in charge of printing the backtrace, or an > external process - like a debugger - would print the backtrace, while > the program is stopped (or after copying the stack for instrospection, > which dbghelp doesn't provide btw))
Why would it be intrusive? Can't you just take a snapshot of the stack and walk it internally? That must be what StackWalk does, right, as apps often try and grab their own backtraces....
