From: Daniel Jacobowitz <drow@false.org>
To: jf <jf@danglingpointers.net>
Cc: gdb@sourceware.org
Subject: Re: signals in a multithreaded application
Date: Fri, 05 Jan 2007 00:58:00 -0000 [thread overview]
Message-ID: <20070105005844.GA5296@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0701050825510.23528@localhost.localdomain>
On Fri, Jan 05, 2007 at 08:35:03AM +0000, jf wrote:
> And the program continues running fine (minus of course the heap
> corruption). Has anyone encountered this before? I changed the settings in
> GDB telling it to not pass the exception to the application thinking that
> the terminal was just messing up or similar and it just happened at the
> same time GDB decided to switch threads (is that GDB changing threads or
> the OS??), but I found that the signal is never delivered.
It's GDB switching threads. But no, I've never seen anything like
this.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-01-05 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 0:53 jf
2007-01-05 0:58 ` Daniel Jacobowitz [this message]
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=20070105005844.GA5296@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jf@danglingpointers.net \
/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