From: Jeff Jenkins <jjenkins@jetstream.com>
To: Jeff Jenkins <jjenkins@jetstream.com>,
"'Gdb (E-mail) '" <gdb@sourceware.cygnus.com>
Subject: RE: Real-Time signals & GDB
Date: Mon, 04 Sep 2000 17:54:00 -0000 [thread overview]
Message-ID: <27A2DAA6CAD9D311BF970050DACB2250013E571F@mail.jetstream.com> (raw)
Sorry that I didn't include this information initally. It was the second
time I posted a similar question.
I am using gdb 4.18 on Solaris 7/SPARC UltraIII.
When I send an RT signal to another thread in my process gdb halts and
complains that it received an unknown ? signal. When I continue, it fails
to deliver the signal. The signal I am typically sending is RT signal 39 or
40. Depends on the thread.
I have tried using handle all to handle ALL threads...I want them delivered
to my process so that I may handle them. I do have other threads in
sigwaitinfo() calls waiting on RT signal 39 & 40.
-- jrj
-----Original Message-----
From: Jeff Jenkins
To: Gdb (E-mail)
Sent: 9/1/00 11:17 AM
Subject: Real-Time signals & GDB
Anyone here know how to get GDB to properly handle RT signals? When I
queue a RT signal, GDB complains that it received an unknown signal and
fails to deliever it to the process. Is there something specific I need
to do such that GDB will handle RT signals?
Thanks!
-- jrj
next reply other threads:[~2000-09-04 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-04 17:54 Jeff Jenkins [this message]
2000-09-04 21:04 ` Mark Kettenis
-- strict thread matches above, loose matches on Subject: below --
2000-09-11 9:10 Jeff Jenkins
2000-09-06 8:15 Jeff Jenkins
2000-09-07 1:41 ` Mark Kettenis
2000-09-10 8:20 ` Peter.Schauer
2000-09-01 11:19 Jeff Jenkins
2000-09-01 11:25 ` Mark Kettenis
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=27A2DAA6CAD9D311BF970050DACB2250013E571F@mail.jetstream.com \
--to=jjenkins@jetstream.com \
--cc=gdb@sourceware.cygnus.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).