bt in traces

[Eric Pouech]

Dimitrie O. Paun a écrit :
> On Thu, 19 Feb 2004, Eric Pouech wrote:
> 
> 
>>perhaps the easiest way to implement what you want would be to create a 
>>specific exception (like wine_stack_walk). This exception would be very 
>>close to the one for undefined symbols. You would insert throwing this 
>>except in the places you want in your code, and winedbg would react to 
>>it by printing the stack backtrace of current thread and continue 
>>execution (we could also extend this as a specific kind of breakpoint, 
>>to be set in the debugger)
> 
> 
> Bu if there is already an official MS DLL for doing that, why go though
> all this trobule? Shouldn't we move most of the debugger in there, and
> build the debugger on top of it?
> 
sure (I mentionned it already a couple of times)
but this will be nevertheless intrusive (and as already pointed out, as 
the dbghelp API is designed, the thread must be disabled the whole time 
of stack walking, which makes it a bit more intrusive
A+