At home last night, I upgraded from the SDL 1.0x version to 1.1.1, and
did a clean recompile of my program. Now, it works fine straight from
the command line. But when I try to run it within GDB, it halts during
initialization with an “unknown signal” exception somewhere down in the
pthread library. This is on a fresh Suse6.2 installation.
Any idea what’s causing this, or how to get around it? I can’t live
without GDB!
– Jeff
At home last night, I upgraded from the SDL 1.0x version to 1.1.1, and
did a clean recompile of my program. Now, it works fine straight from
the command line. But when I try to run it within GDB, it halts during
initialization with an “unknown signal” exception somewhere down in the
pthread library. This is on a fresh Suse6.2 installation.
Any idea what’s causing this, or how to get around it? I can’t live
without GDB!
gdb on SuSE doesn’t know about pthreads.
Just hit ‘c’ to continue, and all should be well.
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
Sam Lantinga wrote:
At home last night, I upgraded from the SDL 1.0x version to 1.1.1, and
did a clean recompile of my program. Now, it works fine straight from
the command line. But when I try to run it within GDB, it halts during
initialization with an “unknown signal” exception somewhere down in the
pthread library. This is on a fresh Suse6.2 installation.
Any idea what’s causing this, or how to get around it? I can’t live
without GDB!
gdb on SuSE doesn’t know about pthreads.
use gdb-4.17 on SuSE 6.2 (gets installed by default too AFAIK). The
standard gdb (4.18 SuSE version) on SuSE 6.2 is horribly broken.–
Daniel Vogel My opinions may have changed,
666 @ http://grafzahl.de but not the fact that I am right
Daniel Vogel wrote:
Sam Lantinga wrote:
gdb on SuSE doesn’t know about pthreads.
use gdb-4.17 on SuSE 6.2 (gets installed by default too AFAIK). The
standard gdb (4.18 SuSE version) on SuSE 6.2 is horribly broken.
Yep, there it is. Thanks! Sorry for the post too. Immediately
afterward, I looked up “gdb unknown signal” on DejaNews and found
several hundred articles about the same problem!
But I’m curious about why this didn’t show up with the earlier version
of SDL.