From: Michael Snyder <msnyder@vmware.com>
To: Kari Nalli <kari880@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: gdb and muti threads with recvfrom
Date: Sat, 16 Aug 2008 08:47:00 -0000 [thread overview]
Message-ID: <48A5C9FF.4060403@vmware.com> (raw)
In-Reply-To: <568faa340808150148o45a07ba6t889c2d6e218ee8b0@mail.gmail.com>
Kari Nalli wrote:
> Hi,
>> 2008/8/14 Michael Snyder <msnyder@vmware.com>:
>> Something to do with signals and threads.
>> I think signals in one thread are not supposed to interrupt
>> other threads, but I'm not sure (and it may depend on the OS).
>>
>> Could be that one thread was waiting on a blocking system call,
>> and another thread took a SIGTRAP from a gdb breakpoint or
>> something...
> There where no breakpoints set in this case, can GDB generate signals
> for some reason?
Yes, gdb often sets its own breakpoints without bothering
to tell the user. This is how shared library support is
implemented, for instance, as well as setjump/longjump support,
and potentially others.
prev parent reply other threads:[~2008-08-15 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 17:27 Kari Nalli
2008-08-14 19:49 ` Andreas Schwab
2008-08-15 8:06 ` Michael Snyder
2008-08-15 18:24 ` Kari Nalli
2008-08-16 8:47 ` Michael Snyder [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=48A5C9FF.4060403@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=kari880@gmail.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