Help me creating a proper backtrace log

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
mogorva
Level 4
Level 4
Posts: 107
Joined: Fri Oct 16, 2009 10:27 am

Help me creating a proper backtrace log

Post by mogorva »

I always compile wine from source as per this Wiki page, however when certain apps crash I got a slightly incomplete backtrace log in the console.

Here is an example (the crash is at the very end of the log):
http://pastebin.com/f46930df4
The tested game is the Secret of Monkey Island SE, the corresponding bug is #19405.

As I can see in the output, there is only a memory address(?) at the Backtrace line, and no module or function names in which the crash happened.

What am I doing wrong?

Fedora 12 x86
Wine-1.1.36 from source

Here is my gcc -v output:

Code: Select all

Using built-in specs.
Target: i686-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch=i686 --build=i686-redhat-linux
Thread model: posix
gcc version 4.4.2 20091222 (Red Hat 4.4.2-20) (GCC)
vitamin
Moderator
Moderator
Posts: 6605
Joined: Sat Feb 23, 2008 2:29 pm

Re: Help me creating a proper backtrace log

Post by vitamin »

mogorva wrote:As I can see in the output, there is only a memory address(?) at the Backtrace line, and no module or function names in which the crash happened. What am I doing wrong?
Don't see nothing wrong. The crash seems to happen in either unallocated memory or some generated / extracted code. More looks like some stack / memory corruption to me or jump to the bogus address.
mogorva
Level 4
Level 4
Posts: 107
Joined: Fri Oct 16, 2009 10:27 am

Post by mogorva »

I just compared my crashlog to the attachment someone submitted to Bugzilla (http://bugs.winehq.org/show_bug.cgi?id=19405) and noticed his crashlog contains more info on the crash.
mogorva
Level 4
Level 4
Posts: 107
Joined: Fri Oct 16, 2009 10:27 am

Post by mogorva »

At last! I've found it: I must pass "-gdwarf-2" to CFLAGS in order to get a proper backtrace, including line numbers and function names. :lol:
Locked