Re: Implement a --backtrace-all mode for winedbg

2004-06-12 Thread Eric Pouech
What is a minidump? I saw them mentioned in the todo list but there weren't many details. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/minidump_files.asp

Re: Implement a --backtrace-all mode for winedbg

2004-06-12 Thread Mike Hearn
On Sat, 12 Jun 2004 19:13:05 +0200, Eric Pouech wrote: > well, in that case the mini-dumps are the way to go (even if they don't > have the pre-defined semantics for system wide thread information, but > they do have what you need). This will embed more details that what > you've done (OS versio

Re: Implement a --backtrace-all mode for winedbg

2004-06-12 Thread Eric Pouech
Mike Hearn a écrit : On Fri, 2004-06-11 at 20:55 +0200, Eric Pouech wrote: I'm not sure I understand the purpose of the --backtrace-all. When a user says "I pressed this button and the app hung" it's convenient to have *somewhere* to start from - this is another attack vector. well, in that case t

Re: Implement a --backtrace-all mode for winedbg

2004-06-11 Thread Mike Hearn
On Fri, 2004-06-11 at 20:55 +0200, Eric Pouech wrote: > I'm not sure I understand the purpose of the --backtrace-all. When a user says "I pressed this button and the app hung" it's convenient to have *somewhere* to start from - this is another attack vector. > There's no way you can ensure a comp

Re: Implement a --backtrace-all mode for winedbg

2004-06-11 Thread Eric Pouech
I'm not sure I understand the purpose of the --backtrace-all. There's no way you can ensure a complete synchro between all threads & processes to get a global picture of the whole system, so the option is likely not very useful (except for the threads which are in a wait operation), but you will