Problems with debugging and signals

SDL Development
1

I tried to debug a SDL app using audio, and here is what I get
(you can reproduce it by running gdb on loopwave in the tests directory
of sdl-1.1.2 - just run the program in the debuger with “sample.wav” as
argument) :

Program received signal ?, Unknown signal.
0x400dd58b in __sigsuspend (set=0xbffff5fc)
at …/sysdeps/unix/sysv/linux/sigsuspend.c:48
48 …/sysdeps/unix/sysv/linux/sigsuspend.c: Aucun fichier ou
r?pertoire de ce type.

After this, the debugger is stuck (Can not continue execution).
Is there a way to avoid this (without disabling audio) ?

(please answer directly by email if possible).

2

Emmanuel Anne wrote:

Program received signal ?, Unknown signal.
0x400dd58b in __sigsuspend (set=0xbffff5fc)
at …/sysdeps/unix/sysv/linux/sigsuspend.c:48
48 …/sysdeps/unix/sysv/linux/sigsuspend.c: Aucun fichier ou
r?pertoire de ce type.

Been there. The problem is that the version of gdb you’re using doesn’t
handle multi-threaded programs. If you’re using SuSE Linux, you already
have the solution: just use gdb-4.17 instead of gdb (which is likely
4.18). If RedHat or another dist., you may have to download it.

3

Jeff Freedman wrote:

Emmanuel Anne wrote:

Program received signal ?, Unknown signal.
0x400dd58b in __sigsuspend (set=0xbffff5fc)
at …/sysdeps/unix/sysv/linux/sigsuspend.c:48
48 …/sysdeps/unix/sysv/linux/sigsuspend.c: Aucun fichier ou
r?pertoire de ce type.

Been there. The problem is that the version of gdb you’re using doesn’t
handle multi-threaded programs. If you’re using SuSE Linux, you already
have the solution: just use gdb-4.17 instead of gdb (which is likely
4.18). If RedHat or another dist., you may have to download it.

Thank you very much !!!

4

im having the same problem, what exactly doi need to download to get it to
work? (im using slackware 7)
i got gdb-4.17 and compiled it and it still didnt work right, is there a
patch or something i need to apply? and were can i get it

Thanks,
Jess
Emmanuel Anne wrote:> Jeff Freedman wrote:

Emmanuel Anne wrote:

Program received signal ?, Unknown signal.
0x400dd58b in __sigsuspend (set=0xbffff5fc)
at …/sysdeps/unix/sysv/linux/sigsuspend.c:48
48 …/sysdeps/unix/sysv/linux/sigsuspend.c: Aucun fichier ou
r?pertoire de ce type.

Been there. The problem is that the version of gdb you’re using doesn’t
handle multi-threaded programs. If you’re using SuSE Linux, you already
have the solution: just use gdb-4.17 instead of gdb (which is likely
4.18). If RedHat or another dist., you may have to download it.

Thank you very much !!!

5

I don’t know the exact answer to your question, but There’s a great page
with some tips on debugging with the latest versions of gdb/gcc on the
Mozilla web site:

http://www.mozilla.org/unix/debugging-faq.html#SIG32

This is an interesting page anyway, and has some talk about stray signals
with pthreads.

Francis> -----Original Message-----

From: Jess
Sent: 13 April 2000 10:25
To: sdl at lokigames.com
Subject: [SDL] Re: problems with debugging and signals

im having the same problem, what exactly doi need to download
to get it to
work? (im using slackware 7)
i got gdb-4.17 and compiled it and it still didnt work right,
is there a
patch or something i need to apply? and were can i get it

Thanks,
Jess
Emmanuel Anne wrote:

Jeff Freedman wrote:

Emmanuel Anne wrote:

Program received signal ?, Unknown signal.
0x400dd58b in __sigsuspend (set=0xbffff5fc)
at …/sysdeps/unix/sysv/linux/sigsuspend.c:48
48 …/sysdeps/unix/sysv/linux/sigsuspend.c: Aucun
fichier ou

r?pertoire de ce type.

Been there. The problem is that the version of gdb
you’re using doesn’t

handle multi-threaded programs. If you’re using SuSE
Linux, you already

have the solution: just use gdb-4.17 instead of gdb
(which is likely

4.18). If RedHat or another dist., you may have to download it.

Thank you very much !!!