-
Notifications
You must be signed in to change notification settings - Fork 0
2.3 beta4 segfaults immediately upon startup on Linux x64 #1262
Comments
Zarel edited the issue description |
Zarel commented That's not a very useful crashdump. At the very least, do Please see this: |
cybersphinx commented Why do you use gdb manually? Don't the automatic crashdumps work for you? |
anonymous commented Here's what I get from the bt full: #0 0x00007fffed86cba0 in ?? () |
anonymous commented For some reason, it doesn't seem to be detecting the debugging symbols, even though they are installed. |
stiv commented Recompile with debug turned on: |
stiv commented Replying to Warzone2100/old-trac-import#1262 (comment:6):
Oops. make the ./configure --enable-debug=yes |
cybersphinx commented Hm, building your package from source on a Debian unstable system works, it starts normally, and the crashdumps (--crash to test) also work. Probably Ubuntu screwed something up again. --enable-debug is not needed, as long as you have -g in your CFLAGS (and not even recommended, since it enables asserts). --with-opengl is useless, btw, since the game doesn't work without OpenGL. --with-ogg shouldn't be needed as well. |
michael@... commented Should I file a bug on Launchpad? Which package do you think might be causing this problem? |
cybersphinx commented dh_strip, which makes the -dbg package, is in debhelper. For the Warzone crash, can you just compile the source with ./configure&&make, then run src/warzone2100? That should give a good crashdump. |
michael@... commented I tried building manually, but no crashdump is given. The GDB output was exactly the same. I can tell you, however, that it has something to do with sound, because running with --nosound works correctly. (except for the lack of audio output, of course) |
cybersphinx commented Can you downgrade OpenAL (to 1.4 or something like that)? That might help. Though it is strange that the crashdumps don't work... |
michael@... commented I tried downgrading OpenAL to version 1.9 (the last released version in Lucid) and both my custom compiled version and the packaged one now work. I will file a bug in OpenAL for ubuntu. |
cybersphinx commented Ok, that solves the crash... still leaves the question of the crashdumps. Do you have any CFLAGS set that override the ones in debian/rules? |
michael@... commented I don't think so. All I did was download the source for an older version, update to the source for 2.3 beta4, and then change the version number in the changelog. And the crashdumps didn't work with the ./configure&&make build either. |
cybersphinx commented Hm, the original problem is solved, so I guess we could close this ticket... but I really don't like having binaries where the crashdumps don't work. What does "set|grep FLAGS" say on your system? |
michael@... commented The only output is: CRLF |
cybersphinx commented What? That doesn't even make sense, how does grep find "FLAGS" in there? |
michael@... commented Carriage return+Line feed It doesn't output anything. |
cybersphinx changed status from |
cybersphinx set resolution to |
cybersphinx commented Oh. Ok. Well, I tested your binary packages here, and whatever prevents the crashdumps from being created is local to your system, it works here. Though I noticed you use --with-distributor=Debian in debian/rules, you should change that. |
resolution_external
type_bug
| by michael@...I have compiled version 2.3 beta4 from source as a debian/ubuntu package in my PPA here: https://edge.launchpad.net/~thefirstm/+archive/lucid. However, whenever I attempt to run it on my x64 system, it displays a black screen for a fraction of a second and then segfaults. I tried installing the debug package and running it with GDB, and here is the output:
Issue migrated from trac:1262 at 2022-04-15 20:18:33 -0700
The text was updated successfully, but these errors were encountered: