Debugging tipps anyone?

[Michael Schwendt]

On Tue, 14 Jun 2005 13:43:39 +0200, Enrico Scholz wrote:

> > 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.
> > ...
> >   Program received signal SIGSEGV, Segmentation fault.
> >   [Switching to Thread 54066096 (zombie)]
> >   0x00a353a8 in ?? ()
> > ...
> > Suggestions, ideas, or hints much appreciated.
> 
> 'valgrind --db-attach=yes --tool=memcheck wesnoth' would be my first
> idea...

Indicates a similar direction (SDL->pthreads usage)...

==9255== 
==9255== Thread 4:
==9255== Jump to the invalid address stated on the next line
==9255==    at 0x1BAC23A8: ???
==9255==    by 0x26BB8D: start_thread (in /lib/libpthread-2.3.5.so)
==9255==    by 0xC79DED: clone (in /lib/libc-2.3.5.so)
==9255==  Address 0x1BAC23A8 is not stack'd, malloc'd or (recently) free'd
==9255== 
==9255== ---- Attach to debugger ? --- [Return/N/n/Y/y/C/c] ---- 



-- 
Fedora Core release 4 (Stentz) - Linux 2.6.11-1.1369_FC4
loadavg: 1.26 1.49 2.20