Floating point exception
Floating point exception
After playing a skirmish game for about 30 minutes, warzone hits a Floating point exception, see the .gdmp file below.
--------------
# cat /tmp/warzone2100.gdmp
Program command: /usr/local/cvs/warzone/trunk/src/warzone2100
Version: TRUNK
Compiled on: Mar 2 2007
Operating system: Linux
Node name: sander
Release: 2.6.19-1.2911.fc6
Version: #1 SMP Sat Feb 10 15:51:47 EST 2007
Machine: i686
Dump caused by signal: Floating point exception
/usr/local/cvs/warzone/trunk/src/warzone2100[0x8171e1e]
[0x33b420]
/usr/local/cvs/warzone/trunk/src/warzone2100[0x804fb36]
/usr/local/cvs/warzone/trunk/src/warzone2100[0x80568fe]
/usr/local/cvs/warzone/trunk/src/warzone2100[0x8073b7e]
/usr/local/cvs/warzone/trunk/src/warzone2100[0x80a639d]
/usr/local/cvs/warzone/trunk/src/warzone2100[0x80a74ae]
/lib/libc.so.6(__libc_start_main+0xdc)[0xae5f2c]
/usr/local/cvs/warzone/trunk/src/warzone2100[0x804c4c1]
--------------
# cat /tmp/warzone2100.gdmp
Program command: /usr/local/cvs/warzone/trunk/src/warzone2100
Version: TRUNK
Compiled on: Mar 2 2007
Operating system: Linux
Node name: sander
Release: 2.6.19-1.2911.fc6
Version: #1 SMP Sat Feb 10 15:51:47 EST 2007
Machine: i686
Dump caused by signal: Floating point exception
/usr/local/cvs/warzone/trunk/src/warzone2100[0x8171e1e]
[0x33b420]
/usr/local/cvs/warzone/trunk/src/warzone2100[0x804fb36]
/usr/local/cvs/warzone/trunk/src/warzone2100[0x80568fe]
/usr/local/cvs/warzone/trunk/src/warzone2100[0x8073b7e]
/usr/local/cvs/warzone/trunk/src/warzone2100[0x80a639d]
/usr/local/cvs/warzone/trunk/src/warzone2100[0x80a74ae]
/lib/libc.so.6(__libc_start_main+0xdc)[0xae5f2c]
/usr/local/cvs/warzone/trunk/src/warzone2100[0x804c4c1]
- DevUrandom
- Regular
- Posts: 1690
- Joined: 31 Jul 2006, 23:14
Re: Floating point exception
Without the binary the return addresses in the backtrace are useless.
Apparenty for SVN compilations the gdmp is informative about the environment, but doesn't help to discover the problem.
What might help a little bit is if you compile warzone with CFLAGS=-rdynamic.
Or send me the binary you compiled. (Only helpful if you compiled it with CFLAGS=-g, which should be done by default.)
Another option is to extract the debugging informations from the binary and set only that. (Might make the file a little bit smaller.)
Do it like this:
'warzone2100' names the binary and 'warzone2100.dbg' the file with the extracted debug informations.
Sorry if you feel a little bit like a guinea pig. We don't have much experiences with the way GLibC creates backtraces and thus still need to find out what is most convenient for our users. It might even turn out that the gdmps are not helpfull at all. We don't know that yet.
Apparenty for SVN compilations the gdmp is informative about the environment, but doesn't help to discover the problem.
What might help a little bit is if you compile warzone with CFLAGS=-rdynamic.
Or send me the binary you compiled. (Only helpful if you compiled it with CFLAGS=-g, which should be done by default.)
Another option is to extract the debugging informations from the binary and set only that. (Might make the file a little bit smaller.)
Do it like this:
Code: Select all
objcopy --only-keep-debug warzone2100 warzone2100.dbg
Sorry if you feel a little bit like a guinea pig. We don't have much experiences with the way GLibC creates backtraces and thus still need to find out what is most convenient for our users. It might even turn out that the gdmps are not helpfull at all. We don't know that yet.
Re: Floating point exception
I have made a warzone2100.dbg file (3.2Mb), where to can I send the file ? I don't see an emailadres in your profile.DevUrandom wrote: Without the binary the return addresses in the backtrace are useless.
Apparenty for SVN compilations the gdmp is informative about the environment, but doesn't help to discover the problem.
What might help a little bit is if you compile warzone with CFLAGS=-rdynamic.
Or send me the binary you compiled. (Only helpful if you compiled it with CFLAGS=-g, which should be done by default.)
Another option is to extract the debugging informations from the binary and set only that. (Might make the file a little bit smaller.)
Do it like this:'warzone2100' names the binary and 'warzone2100.dbg' the file with the extracted debug informations.Code: Select all
objcopy --only-keep-debug warzone2100 warzone2100.dbg
Sorry if you feel a little bit like a guinea pig. We don't have much experiences with the way GLibC creates backtraces and thus still need to find out what is most convenient for our users. It might even turn out that the gdmps are not helpfull at all. We don't know that yet.
- DevUrandom
- Regular
- Posts: 1690
- Joined: 31 Jul 2006, 23:14
Re: Floating point exception
You can attach it (and up to 5MB) to your posting.
Re: Floating point exception
DevUrandom wrote: You can attach it (and up to 5MB) to your posting.
- Attachments
-
[The extension has been deactivated and can no longer be displayed.]
- DevUrandom
- Regular
- Posts: 1690
- Joined: 31 Jul 2006, 23:14
Re: Floating point exception
Probably the same bug as: https://gna.org/bugs/?8723