From: "ying lcs" <yinglcs@gmail.com>
To: gdb@sourceware.org
Subject: Program received signal SIG33, Real-time event 33.
Date: Sun, 02 Sep 2007 05:54:00 -0000 [thread overview]
Message-ID: <568e62a40709012254j43aa5c15i9c7612350a77de55@mail.gmail.com> (raw)
Hi,
I am getting a 'Program received signal SIG33, Real-time event 33'
when I run my program under gdb for debugging.
Can you please tell me why? and how can I run it under gdb?
The program starts fine if I run it straight from command prompt.
Here is the detailed message:
[root@localhost DarwinStreamingSrvr5.5.5-Source]# ./gdbdar
GNU gdb Red Hat Linux (6.3.0.0-1.122rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host
libthread_db library "/lib/libthread_db.so.1".
(gdb) source gdb_script
(gdb) run -d -s 5
Starting program:
/home/yinglcs/DarwinStreamingSrvr5.5.5-Source/DarwinStreamingServer -d
-s 5
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0xc34000
[Thread debugging using libthread_db enabled]
[New Thread -1208932160 (LWP 2510)]
[New Thread -1208935520 (LWP 2513)]
[New Thread -1219425376 (LWP 2514)]
[New Thread -1229972576 (LWP 2517)]
Program received signal SIG33, Real-time event 33.
[Switching to Thread -1208932160 (LWP 2510)]
0x00b28a64 in __nptl_create_event () from /lib/libpthread.so.0
next reply other threads:[~2007-09-02 5:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 5:54 ying lcs [this message]
2007-09-02 7:50 ` Petr Vandrovec
2007-09-02 13:44 ` Daniel Jacobowitz
2007-09-03 2:24 ` Petr Vandrovec
2007-09-03 3:07 ` ying lcs
2007-09-03 7:47 ` Mark Kettenis
2007-09-03 8:04 ` Petr Vandrovec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=568e62a40709012254j43aa5c15i9c7612350a77de55@mail.gmail.com \
--to=yinglcs@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox