0.11.2 segfaults at Multithreading

I compiled SDL 0.11.2 on my SuSE 6.2 system using egcs 1.1.2 and
everything went fine. Most of the test-programs work, except one:
testhread segfaults and shows me the SDL-Parachute, and so does every
other program that uses SDL and tries to do multithreading (e.g. smpeg).

Any hints?–
/E-Mail: @Stefan_Tomanek | ICQ: 1177934 | Ask for CA-signed PGP-Key/
/Spielen unter Linux: http://spiele.freepage.de/linux-zocker/ /
/“We are M$ of Borg. We will add your technology to our own crap. /
/Your company will be bought. Open Source is futile!” /

hi`

Stefan Tomanek wrote:

I compiled SDL 0.11.2 on my SuSE 6.2 system using egcs 1.1.2 and
everything went fine. Most of the test-programs work, except one:
testhread segfaults and shows me the SDL-Parachute, and so does every
other program that uses SDL and tries to do multithreading (e.g. smpeg).

I use SDL 0.11.2, SuSE 6.2 and gcc 2.91.66 (aka egcs 1.1.2) too and
everything works perfect for me.

Any hints?

a backtrace would be helpfull…–
Daniel Vogel

666 @ http://grafzahl.de

hi`

Stefan Tomanek wrote:

I compiled SDL 0.11.2 on my SuSE 6.2 system using egcs 1.1.2 and
everything went fine. Most of the test-programs work, except one:
testhread segfaults and shows me the SDL-Parachute, and so does every
other program that uses SDL and tries to do multithreading (e.g. smpeg).

Any hints?

You are not running these programs under gdb, right? SuSE 6.2 comes with
gdb 4.18 as the standard gdb, but sadly it cannot handle LinuxThreads
and therefore gets confused by the signals threads use for communication
leading to gdb catching unknown signals and going berserk…

Use gdb-4.17 for debugging apps that use LinuxThreads (and for a
backtrace eg.). Btw, the CVS version of GDB (~9MByte) works with
LinuxThreads, too.–
Daniel Vogel

666 @ http://grafzahl.de