Version-Release number of selected component: extremetuxracer-0.4-10.fc18 Additional info: backtrace_rating: 4 cmdline: etracer core_backtrace: crash_function: dequeue_pending_request executable: /usr/bin/etracer kernel: 3.8.2-206.fc18.i686.PAE uid: 1000 var_log_messages: Mar 13 13:54:27 kraak-PC abrt[2054]: Saved core dump of pid 2021 (/usr/bin/etracer) to /var/spool/abrt/ccpp-2013-03-13-13:54:27-2021 (91795456 bytes) Truncated backtrace: Thread no. 1 (10 frames) #5 dequeue_pending_request at xcb_io.c:184 #8 XSync at src/video/x11/SDL_x11sym.h:104 #9 X11_VideoQuit at src/video/x11/SDL_x11video.c:1493 #10 SDL_VideoQuit at src/video/SDL_video.c:1365 #11 SDL_QuitSubSystem at src/SDL.c:196 #12 SDL_Quit at src/SDL.c:222 #13 SDL_Parachute at src/SDL_fatal.c:41 #15 ?? #16 pt_playeffects at ../playercode/mplayer.c:2237 #17 pt_EffectsPass1 at ../playercode/mplayer.c:2671 Potential duplicate: bug 857415
Created attachment 709566 [details] File: backtrace
Created attachment 709567 [details] File: cgroup
Created attachment 709568 [details] File: dso_list
Created attachment 709569 [details] File: environ
Created attachment 709570 [details] File: limits
Created attachment 709571 [details] File: maps
Created attachment 709572 [details] File: open_fds
Created attachment 709573 [details] File: proc_pid_status
The crash happens a few frames deep in /usr/lib/libmikmod.so.3.0.0, changing component to libmikmod.
This is the original crash location, the later SIGABRT is just a followup error: #13 0x43334dc0 in SDL_Parachute (sig=11) at src/SDL_fatal.c:41 No locals. #14 <signal handler called> No symbol table info available. #15 0x00000001 in ?? () No symbol table info available. #16 0xb07df03f in pt_playeffects (a=0x966ced0, channel=<optimized out>, mod=0x963eb20) at ../playercode/mplayer.c:2237 --> It seems as if frame #16 calls an invalid function pointer.
Hi Enjo, Thanks for the bug report, which version of libmikmod are you using? Can you please provide the output of "rpm -q libmikmod", and also of "rpm --verify libmikmod" ? Thank, Hans
Hi Again, I believe this is a libmikmod bug which has been fixed recently, so I'm going to mark this as a duplicate of that bug. Please make sure you've libmikmod >= 3.2.0-19. If you see this bug again with libmikmod >= 3.2.0-19, please let abrt file a new bug. Regards, Hans *** This bug has been marked as a duplicate of bug 859050 ***