Robert Shearman rob@codeweavers.com writes:
Alexandre Julliard wrote:
Well, I can also imagine a lot of cases where the in-process backtrace won't work right, the main one being that since the code will never be used unless you want a backtrace, when you try to use it you'll realize that it no longer works, or doesn't even compile anymore. If we call the debugger instead, it will use the standard backtrace code which is always compiled in, and regularly used by a lot of people.
Do you want me to write a unit test that uses it then?
No, the backtrace should be done by the debugger.