From: "Frank Ch. Eigler" <fche@redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: sid@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: sid debugger interface extension: step out-of-range packet support
Date: Fri, 22 Feb 2002 19:28:00 -0000 [thread overview]
Message-ID: <20020222222851.A17206@redhat.com> (raw)
In-Reply-To: <3C76E8F3.673C6559@redhat.com>; from msnyder@redhat.com on Fri, Feb 22, 2002 at 04:57:23PM -0800
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
Hi -
msnyder wrote:
> [...]
> Thanks for pointing out this problem, which is in fact
> more severe than you think.
>
> A quick experiment reveals that if you
> 1) put a breakpoint at the beginning of line N
> 2) put a second breakpoint in the MIDDLE of line N
> 3) attempt to step over line N
> the second breakpoint will not be hit.
Interesting, but at least it's an unusual debugging
usage scenario.
> And in fact, if you have a multi-threaded program,
> all threads will have the opportunity to run (if they
> are runnable), and NONE of them will hit ANY breakpoints
> while we are executing line N. This will give threads
> the opportunity to "run away".
No, I think that's only if the other threads all happen also
to be executing the same line N. If any passes outside, then
the step-out-of-range process would abort, as the 'e' packet
is no more thread-specific than 's' is.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-02-23 3:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 14:14 Frank Ch. Eigler
2002-02-12 22:10 ` Andrew Cagney
2002-02-13 7:13 ` Frank Ch. Eigler
2002-02-13 12:52 ` Andrew Cagney
2002-02-22 17:08 ` Michael Snyder
2002-02-22 17:05 ` Michael Snyder
2002-02-22 19:28 ` Frank Ch. Eigler [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=20020222222851.A17206@redhat.com \
--to=fche@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=msnyder@redhat.com \
--cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).