public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
	utrace-devel@redhat.com, "Frank Ch. Eigler" <fche@redhat.com>,
	archer@sourceware.org
Subject: Re: ugdb && breakpoints
Date: Tue, 14 Sep 2010 19:38:00 -0000	[thread overview]
Message-ID: <20100914193804.99980403E8@magilla.sf.frob.com> (raw)
In-Reply-To: Tom Tromey's message of  Friday, 10 September 2010 16:12:12 -0600 <m3aanpjlj7.fsf@fleche.redhat.com>

The traditional method is to restore the original instruction replaced by
the breakpoint in text, single-step over that instruction, then restore the
breakpoint in text, then continue.  That method requires all-stop so that
while you are stepping the thread that just hit the breakpoint, you can't
have another thread run past that instruction and miss the breakpoint.

Both this traditional in-place method, and the instruction-copying method,
depend on using single-step.  So "stepi" has to work before "break" can work.


Thanks,
Roland

  reply	other threads:[~2010-09-14 19:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 19:22 gdbstub initial code, v9 Oleg Nesterov
2010-09-09 10:29 ` Jan Kratochvil
2010-09-09 15:06   ` Oleg Nesterov
2010-09-09 12:39 ` Frank Ch. Eigler
2010-09-09 15:33   ` Oleg Nesterov
2010-09-09 15:54     ` Oleg Nesterov
2010-09-09 16:07       ` Frank Ch. Eigler
2010-09-09 16:37         ` Oleg Nesterov
2010-09-09 16:11       ` Jan Kratochvil
2010-09-09 16:34         ` Oleg Nesterov
2010-09-09 16:36           ` Jan Kratochvil
2010-09-09 16:48             ` Oleg Nesterov
2010-09-09 16:50               ` Oleg Nesterov
2010-09-09 16:51               ` Tom Tromey
2010-09-10 10:12                 ` Roland McGrath
2010-09-10 18:14                   ` Oleg Nesterov
2010-09-10 19:43                     ` Tom Tromey
2010-09-10 19:49                       ` Oleg Nesterov
2010-09-13  5:54     ` Kevin Buettner
2010-09-14  2:20       ` Roland McGrath
2010-09-14 16:10         ` Oleg Nesterov
2010-09-14 16:30           ` Jan Kratochvil
2010-09-14 21:30             ` Tom Tromey
2010-09-15 19:43           ` Kevin Buettner
2010-09-10 22:03   ` ugdb && breakpoints Oleg Nesterov
2010-09-10 22:12     ` Tom Tromey
2010-09-14 19:38       ` Roland McGrath [this message]
2010-09-14 19:47         ` Oleg Nesterov

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=20100914193804.99980403E8@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=archer@sourceware.org \
    --cc=fche@redhat.com \
    --cc=oleg@redhat.com \
    --cc=tromey@redhat.com \
    --cc=utrace-devel@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).