Red Hat Bugzilla – Bug 162402
gdb can't continue after receiving SIG33
Last modified: 2007-11-30 17:11:09 EST
Description of problem:
While using gdb on a debug version of Mozilla and loading a particular page
(with flash), gdb breaks and reports that "Program received signal SIG33,
Real-time event 33." Trying to continue produces more of these (one per thread,
perhaps) and then Mozilla seems to hang. Mozilla does not hang if not running
under gdb. Also (unfortunately), non-debug builds of Mozilla do not have this
I'm attaching a HTML testcase which causes the problem (not all pages with flash
have this problem).
Version-Release number of selected component (if applicable):
current Mozilla (SeaMonkey) trunk. Firefox /hates/ gdb so I can't test it.
Program received signal SIG33, Real-time event 33.
[Switching to Thread -1243194448 (LWP 28948)]
0x00eee402 in __kernel_vsyscall ()
#0 0x00eee402 in __kernel_vsyscall ()
#1 0x00a66a1c in pthread_cond_timedwait@@GLIBC_2.3.2 ()
#2 0x00e9c4da in pt_TimedWait (cv=0x9c4a974, ml=0x9c4a910, timeout=60000)
#3 0x00e9c8f6 in PR_WaitCondVar (cvar=0x9c4a970, timeout=60000)
Created attachment 116318 [details]
A workaround is to do "handle SIG33 nostop noprint pass" before running or
continuing a threaded program.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
I don't see this bug with the attached testcase with FC6's gdb.