From: Jon Ringle <jon@ringle.org>
To: Jon Ringle <jon@ringle.org>,
Michael Snyder <Michael.Snyder@palmsource.com>,
gdb@sourceware.org
Subject: Re: [SPAM] Re: gdbserver signals interfere with {next,step{,i}}
Date: Tue, 06 Mar 2007 14:57:00 -0000 [thread overview]
Message-ID: <45ED814D.1040409@ringle.org> (raw)
In-Reply-To: <20070306143928.GA29866@caradoc.them.org>
Daniel Jacobowitz wrote:
> It may have decided that they are used by uClibc's threading library.
> Beyond here I do not think I can make any useful guesses; all the
> logic is different between gdb and gdbserver. You'd have to debug it.
>
> If it's decided threading uses them, "handle SIGUSR1" should show
> nostop noprint alreayd. Otherwise, it may just never be notified of
> the signal - that would be a bug somewhere.
>
>
Sorry, my bad here. I had been playing around with using different
signals last night and left the code using SIGALRM instead, which
defaults to nostop noprint. When I switched back to using SIGUSR1 again,
I had to use 'handle SIGUSR1 nostop noprint' on the native gdb.
Jon
next prev parent reply other threads:[~2007-03-06 14:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 20:06 Jon Ringle
2007-03-05 20:17 ` Daniel Jacobowitz
2007-03-05 23:20 ` Jon Ringle
2007-03-06 1:43 ` Michael Snyder
2007-03-06 1:48 ` [SPAM] " Jon Ringle
2007-03-06 2:11 ` Michael Snyder
2007-03-06 2:25 ` [SPAM] " Jon Ringle
2007-03-06 12:25 ` Daniel Jacobowitz
2007-03-06 14:31 ` Jon Ringle
2007-03-06 14:39 ` Daniel Jacobowitz
2007-03-06 14:57 ` Jon Ringle [this message]
2007-03-06 19:46 ` Michael Snyder
2007-03-06 20:18 ` Jon Ringle
2007-03-06 20:19 ` Daniel Jacobowitz
2007-03-06 19:41 ` Michael Snyder
2007-03-06 20:10 ` Jon Ringle
2007-03-06 2:40 ` Jon Ringle
2007-03-06 5:07 ` Jon Ringle
2007-03-06 1:17 ` Michael Snyder
2007-03-06 1:30 ` Jon Ringle
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=45ED814D.1040409@ringle.org \
--to=jon@ringle.org \
--cc=Michael.Snyder@palmsource.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