no backtrace in console

chourmovs · Post by **chourmovs** » Thu May 29, 2008 12:45 am

buggzilla maintainer tell me "there's no backtrace in console output" in comment to my newly posted bug

here is the bug: http://bugs.winehq.org/show_bug.cgi?id=13450

i don't understand this and if i have something to do
Thank you for explanations

Vincent

vitamin · Post by **vitamin** » Thu May 29, 2008 7:29 am

chourmovs wrote:buggzilla maintainer tell me "there's no backtrace in console output" in comment to my newly posted bug

here is the bug: http://bugs.winehq.org/show_bug.cgi?id=13450

i don't understand this and if i have something to do
Thank you for explanations

Usually when something crashes Wine attaches it's own debugger and generating a backtrace of the crash. In some cases, programs might intercept this and create their own "bug report", "crash dump" or just "memory dump".

If you don't get a backtrace from Wine, then try to find that other report and attach it. Or if it's a memory dump - load it with winedbg and do 'bt all'. Then attach the output.

chourmovs · Post by **chourmovs** » Thu May 29, 2008 11:50 am

woow

maybe i have to read the documentation for a "how to" ....

Thank you

austin987 · Post by **austin987** » Thu May 29, 2008 11:58 am

On Thu, May 29, 2008 at 11:50 AM, chourmovs <[email protected]> wrote:

woow

maybe i have to read the documentation for a "how to" ....

Thank you

Pretty simple:

Open two terminals:
Terminal 1:
$ wine your_app.exe #crash, but no backtrace

Terminal 2:
$ winedbg

bt all

Copy and paste into text file, and attach to bug.

Greyvend · Post by **Greyvend** » Thu Jul 12, 2012 11:16 pm

And what to do if the application closes immediately after crushing?