Re: winedbg: Fix 'winedbg --auto' so it does just one backtrace.
Francois Gouget <fgouget(a)codeweavers.com> writes:
'winedbg --auto' already prints a backtrace before the modules list. So there is no need to print another one after everything else.
Actually there are cases where it doesn't, which is why I added this. It's better to have two backtraces than none. -- Alexandre Julliard julliard(a)winehq.org
Alexandre Julliard a écrit :
Francois Gouget <fgouget(a)codeweavers.com> writes:
'winedbg --auto' already prints a backtrace before the modules list. So there is no need to print another one after everything else.
Actually there are cases where it doesn't, which is why I added this. It's better to have two backtraces than none.
can you reproduce those cases ? it may be even better to fix those cases instead of having two backtraces <g> A+ -- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)
Eric Pouech <eric.pouech(a)orange.fr> writes:
Alexandre Julliard a écrit :
Actually there are cases where it doesn't, which is why I added this. It's better to have two backtraces than none.
can you reproduce those cases ? it may be even better to fix those cases instead of having two backtraces <g>
Yes, that would be better, but I'm afraid I don't remember where I ran into that. I'll let you know if I see it again. -- Alexandre Julliard julliard(a)winehq.org
participants (2)
-
Alexandre Julliard -
Eric Pouech