Debugging tipps anyone?

Michael Schwendt fedora at wir-sind-cool.org
Tue Jun 14 10:16:38 UTC 2005


This is the result of last night's attempt at testing whether an updated
version of "wesnoth" 0.9.2 (Fedora Extras) would seem to work with FC4.
Clicking some buttons in its network related menus or connecting to the
official server lead to this fully reproducible crash:

  Program received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 54066096 (zombie)]
  0x00a353a8 in ?? ()
  (gdb) bt
  #0  0x00a353a8 in ?? ()
  #1  0x0026ab7a in __nptl_deallocate_tsd () from /lib/libpthread.so.0
  #2  0x0026bb8e in start_thread () from /lib/libpthread.so.0
  #3  0x00c79dee in clone () from /lib/libc.so.6
  (gdb) t
  [Current thread is 4 (Thread 54066096 (zombie))]

It's not reproducible with FC3.

Backtraces for the threads (attached) don't look suspicious IMO. Adding
more debuginfo packages didn't give more detailed output. Two other things
I tried last night was to build without -O2 and build SDL with default optflags
instead of -O3. No change.

Suggestions, ideas, or hints much appreciated.

-- 
Fedora Core release 4 (Stentz) - Linux 2.6.11-1.1369_FC4
loadavg: 1.45 1.33 1.50
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Backtraces2.txt
Url: http://lists.fedoraproject.org/pipermail/devel/attachments/20050614/9936a0dc/attachment-0002.txt 


More information about the devel mailing list