From: David Carlton <carlton@kealia.com>
To: gdb <gdb@sources.redhat.com>
Subject: TARGET_SIGNAL_TRAP
Date: Thu, 17 Jul 2003 18:29:00 -0000 [thread overview]
Message-ID: <yf2isq13t2f.fsf@hawaii.kealia.com> (raw)
Some users here have noted that they have a hard time debugging
multithreaded code in GDB. We're assuming that it's probably a bug in
our code instead of in GDB: it's just that GDB is changing the timing
of the threads in ways that expose a latent bug in our code.
Which made me curious: why does GDB change the timing of programs? I
set a breakpoint in handle_inferior_event, and I see all these events
claiming to be TARGET_SIGNAL_TRAPs. But I haven't set any breakpoints
or watchpoints! So what causes all these traps to be generated? Or
am I misunderstanding the situation? (I'm not at all sure that this
is specific to multithreaded code - it may just be that its effects
are most pronounced for multithreaded code, because single-threaded
code doesn't have as much timing to be thrown off.)
David Carlton
carlton@kealia.com
next reply other threads:[~2003-07-17 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 18:29 David Carlton [this message]
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 ` TARGET_SIGNAL_TRAP Elena Zannoni
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=yf2isq13t2f.fsf@hawaii.kealia.com \
--to=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