From: Elena Zannoni <ezannoni@redhat.com>
To: David Carlton <carlton@kealia.com>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: TARGET_SIGNAL_TRAP
Date: Thu, 17 Jul 2003 19:38:00 -0000 [thread overview]
Message-ID: <16150.64763.357755.892135@localhost.redhat.com> (raw)
In-Reply-To: <yf2d6g93qqo.fsf@hawaii.kealia.com>
David Carlton writes:
> On Thu, 17 Jul 2003 14:32:14 -0400, Daniel Jacobowitz <drow@mvista.com> said:
>
> > Every time that a breakpoint is hit, including one breakpoint set at
> > every shared library load/unload, thread creation, or sometimes thread
> > exit, all threads are stopped and restarted. That's the usual cause.
>
> > Signals also stop the process. If GDB isn't going to report the signal
> > then it doesn't stop all threads, but that does interfere with timing.
>
> Ah, thanks for the info. I wonder if it's the shared library loads
> that we're seeing. Hmm: we might even be able to control that one.
>
> David Carlton
> carlton@kealia.com
try 'maint info break' to see all (kind of) the hidden breakpoints.
elena
prev parent reply other threads:[~2003-07-17 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 18:29 TARGET_SIGNAL_TRAP David Carlton
2003-07-17 18:35 ` TARGET_SIGNAL_TRAP Daniel Jacobowitz
2003-07-17 19:20 ` TARGET_SIGNAL_TRAP David Carlton
2003-07-17 19:38 ` Elena Zannoni [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=16150.64763.357755.892135@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=carlton@kealia.com \
--cc=gdb@sources.redhat.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