| Summary: | Freeciv 2.1.3 compiles fine, but fails to start | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Boyan Ivanov <tindor> |
| Component: | [OLD] Games | Assignee: | Gentoo Games <games> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Output with -d 3 option | ||
|
Description
Boyan Ivanov
2008-04-17 17:05:54 UTC
Created attachment 150088 [details]
Output with -d 3 option
Well, in the description of "severity" it's said if the program crashes, it's critical. It's okay with me though the status to be changed to normal. It start here, same USE flags. Maybe you can build it with FEATURES="nostrip" CFLAGS="-O2 -march=pentium-m -pipe -g" and then start it with gdb to see where it break: gdb civclient ... (gdb) run .... (gdb) bt and analyze the output of the command. That way you can further go and find who is the faulty item You can also try to emerge it using: CFLAGS="-O1 -march=pentium-m -pipe -g" as the freeciv site says: WARNING: gcc 4.2.1 and 4.2.2 miscompile Freeciv, if level -O2 (or above) optimization is used! Maybe it apply to 4.2.3 too. Well, my gcc version is 4.1.2 but tried with -01 and still the problem's there.
I also added "nostrip" but got useless stacktrace, pointing to libgdk file.
Then I reemerged gtk with debug flag and here's a bit more useful stacktrace from civclient :
(gdb) run
Starting program: /usr/games/bin/civclient
[Thread debugging using libthread_db enabled]
[New Thread 0xb73aa6c0 (LWP 4071)]
[New Thread 0xb70b1b90 (LWP 4074)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb73aa6c0 (LWP 4071)]
0xb685c2f2 in ?? ()
(gdb) bt
#0 0xb685c2f2 in ?? ()
#1 0xb7b6a85b in gdk_event_apply_filters (xevent=0xbfe90b3c, event=0x8e7c9f0,
filters=0x82f0b40) at gdkevents-x11.c:345
#2 0xb7b6c264 in gdk_event_translate (display=0x82ce020, event=0x8e7c9f0,
xevent=0xbfe90b3c, return_exposes=0) at gdkevents-x11.c:896
#3 0xb7b6e91e in _gdk_events_queue (display=0x82ce020) at gdkevents-x11.c:2285
#4 0xb7b6edb1 in gdk_event_dispatch (source=0x82d85a0, callback=0,
user_data=0x0) at gdkevents-x11.c:2345
#5 0xb7957b4f in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
Can you test it with the new version of freeciv (2.1.4) just added in portage? It works now, but it wasn't the new version that fixed it. After posting the stacktrace I googled about parts of it and I found out that the problem was due to the gtk-qt engine. After I enabled it from the control center of KDE, everything works fine. I tested it with 2.1.3 and 2.1.4. 2.0.9 has no problems with gtk-qt. clean up bug list after bugzilla update |
