Bygfoot Football Manager

Posted: **Sat Dec 17, 2005 1:57 pm**

** (bygfoot:1922): WARNING **: live_game_create_unit: called after end of match.

compiled from source with gcc 4

I'm going to try the precompiled one

Posted: **Sun Dec 18, 2005 5:20 pm**

Another crash, just after finishing a live game:

** (bygfoot:9250): WARNING **: live_game_event_general: unknown event type: 4

This time it didn't say "Segmentation fault" like in the previous one.

It was quite weird, i tried to pause the live game after the computer was changing his team formation, but the game continued for more than 10 mins. with the "pause" button greyed out so i went and hit "resume", nothing else unusual happened until the crash.

Posted: **Sun Dec 18, 2005 6:35 pm**

Yet another one without warning message, just segmentation fault.

This was in a tied 120min. long final after 6 penalties, the enemy team shoots the 7th or so, fails and... the game segfaults

Posted: **Sun Dec 18, 2005 7:25 pm**

The last one (final of a cup) is crashing always, is the same game as the previous message, already tried 4 times, 4 segfaults...

This is the gdb backtrace:

Code: Select all

(gdb) run
Starting program: /usr/local/bin/bygfoot

Program received signal SIGSEGV, Segmentation fault.
0x407f081a in strcmp () from /lib/tls/libc.so.6
(gdb) bt
#0  0x407f081a in strcmp () from /lib/tls/libc.so.6
#1  0x080acedf in user_history_add ()
#2  0x08062224 in game_post_match ()
#3  0x08077a33 in live_game_resume ()
#4  0x404895eb in g_cclosure_marshal_VOID__VOID () from /opt/gnome/lib/libgobject-2.0.so.0
#5  0x4047cd19 in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0
#6  0x4048c7d4 in g_signal_stop_emission () from /opt/gnome/lib/libgobject-2.0.so.0
#7  0x4048de20 in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0
#8  0x4048e195 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0
#9  0x4009c8e1 in gtk_button_clicked () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#10 0x4009e378 in gtk_button_get_alignment () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#11 0x404895eb in g_cclosure_marshal_VOID__VOID () from /opt/gnome/lib/libgobject-2.0.so.0
#12 0x4047c637 in g_cclosure_new_swap () from /opt/gnome/lib/libgobject-2.0.so.0
#13 0x4047cd19 in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0
#14 0x4048c435 in g_signal_stop_emission () from /opt/gnome/lib/libgobject-2.0.so.0
#15 0x4048de20 in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0
#16 0x4048e195 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0
#17 0x4009c851 in gtk_button_released () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#18 0x4009d89f in gtk_button_set_relief () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#19 0x4016be60 in gtk_marshal_VOID__UINT_STRING () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#20 0x4047c637 in g_cclosure_new_swap () from /opt/gnome/lib/libgobject-2.0.so.0
#21 0x4047cd19 in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0
#22 0x4048c965 in g_signal_stop_emission () from /opt/gnome/lib/libgobject-2.0.so.0
#23 0x4048db92 in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0
#24 0x4048e195 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0
#25 0x4025e3b4 in gtk_widget_activate () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#26 0x4016a265 in gtk_propagate_event () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#27 0x4016a6ff in gtk_main_do_event () from /opt/gnome/lib/libgtk-x11-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#28 0x40370f8a in gdk_screen_get_setting () from /opt/gnome/lib/libgdk-x11-2.0.so.0
#29 0x404dc2cc in g_main_context_dispatch () from /opt/gnome/lib/libglib-2.0.so.0
#30 0x404df72b in g_main_context_check () from /opt/gnome/lib/libglib-2.0.so.0
#31 0x404dfa47 in g_main_loop_run () from /opt/gnome/lib/libglib-2.0.so.0
#32 0x40169861 in gtk_main () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#33 0x0807990a in main ()
(gdb)

Posted: **Mon Dec 19, 2005 4:46 pm**

could you send me a savegame that crashes? that'd help a lot in finding the bug (might be the same bug as the other one you reported, the bt leads to the user history func again).

gyözö

Posted: **Mon Dec 19, 2005 6:00 pm**

Yes, the backtrace is the same bug, but the 2 first messages (the ones with the warning message) were different crashes... i think other people already reported them in other threads.

They seem to happen if you click any button when the game is about to end or when the computer player is doing changes to his team. I'm going to send you the savegame of the backtrace.

Bygfoot Football Manager

1.9.3 Segfault just after ending a match

1.9.3 Segfault just after ending a match