Bug 162402 - gdb can't continue after receiving SIG33
gdb can't continue after receiving SIG33
Product: Fedora
Classification: Fedora
Component: gdb (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jan Kratochvil
Depends On:
  Show dependency treegraph
Reported: 2005-07-04 01:29 EDT by Andrew Schultz
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-19 20:55:51 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
testcase (269 bytes, text/html)
2005-07-04 01:29 EDT, Andrew Schultz
no flags Details

  None (edit)
Description Andrew Schultz 2005-07-04 01:29:43 EDT
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.

Actual results:
Program received signal SIG33, Real-time event 33.
[Switching to Thread -1243194448 (LWP 28948)]
0x00eee402 in __kernel_vsyscall ()
(gdb) bt
#0  0x00eee402 in __kernel_vsyscall ()
#1  0x00a66a1c in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/libpthread.so.0
#2  0x00e9c4da in pt_TimedWait (cv=0x9c4a974, ml=0x9c4a910, timeout=60000)
    at /build/andrew/moz-debug/mozilla/nsprpub/pr/src/pthreads/ptsynch.c:280
#3  0x00e9c8f6 in PR_WaitCondVar (cvar=0x9c4a970, timeout=60000)
    at /build/andrew/moz-debug/mozilla/nsprpub/pr/src/pthreads/ptsynch.c:407
Comment 1 Andrew Schultz 2005-07-04 01:29:44 EDT
Created attachment 116318 [details]
Comment 2 Nicholas Miell 2006-11-11 01:20:44 EST
A workaround is to do "handle SIG33 nostop noprint pass" before running or
continuing a threaded program.
Comment 3 Christian Iseli 2007-01-19 19:20:14 EST
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 ?

Comment 4 Andrew Schultz 2007-01-19 20:55:51 EST
I don't see this bug with the attached testcase with FC6's gdb.

Note You need to log in before you can comment on or make changes to this bug.