0
0

When using my fmod-linked application in gdb, if I hit ctrl-z to break and add a breakpoint, look at variables, etc., I can’t get my application to start up again. If I tell gdb to continue, it just continues to tell me that it received a SIGSTP (user). Here is an example:

[New Thread 32769 (LWP 12826)]
[New Thread 16386 (LWP 12827)]
[New Thread 32771 (LWP 12828)]

Program received signal SIGTSTP, Stopped (user).
[Switching to Thread 16384 (LWP 12825)]
0x40009b58 in _dl_debug_state_internal () from /lib/ld-linux.so.2
(gdb) c
Continuing.

Program received signal SIGTSTP, Stopped (user).
0x40009b58 in _dl_debug_state_internal () from /lib/ld-linux.so.2
(gdb) c
Continuing.

Program received signal SIGTSTP, Stopped (user).
[Switching to Thread 32771 (LWP 12828)]
0x40486671 in nanosleep () from /lib/libc.so.6
(gdb) c
Continuing.

Program received signal SIGTSTP, Stopped (user).
[Switching to Thread 16386 (LWP 12827)]
0x404a3cb4 in write () from /lib/libc.so.6
(gdb) c
Continuing.

Program received signal SIGTSTP, Stopped (user).
[Switching to Thread 32771 (LWP 12828)]
0x40486671 in nanosleep () from /lib/libc.so.6
(gdb) c

(gdb) info thread
* 4 Thread 32771 (LWP 12828) 0x40486671 in nanosleep () from /lib/libc.so.6
3 Thread 16386 (LWP 12827) 0x404a3cb4 in write () from /lib/libc.so.6
2 Thread 32769 (LWP 12826) 0x404a840c in poll () from /lib/libc.so.6
1 Thread 16384 (LWP 12825) 0x404a223d in __xstat () from /lib/libc.so.6

I’ve had this same problem on every linux box I’ve tried this on. If I disable fmod, everything works fine. The windows build of this application also doesn’t have any odd behavior, even with fmod enabled. Is this a bug in gdb, some sort of signal-interception fight between gdb and fmod, or some other unknown quirk?

Thanks,
Jon

  • You must to post comments
Showing 0 results
Your Answer

Please first to submit.