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
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 explanationsUsually 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.
woow :? maybe i have to read the documentation for a "how to" .... Thank you
On Thu, May 29, 2008 at 11:50 AM, chourmovs <wineforum-user at winehq.org> 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 allCopy and paste into text file, and attach to bug.