From: fche@redhat.com (Frank Ch. Eigler)
To: Oleg Nesterov <oleg@redhat.com>
Cc: archer@sourceware.org, utrace-devel@redhat.com
Subject: Re: gdbstub initial code, v9
Date: Thu, 09 Sep 2010 12:39:00 -0000 [thread overview]
Message-ID: <y0my6bbccqs.fsf@fche.csb> (raw)
In-Reply-To: <20100908191838.GA27120@redhat.com> (Oleg Nesterov's message of "Wed, 8 Sep 2010 21:18:38 +0200")
Oleg Nesterov <oleg@redhat.com> writes:
> [...]
> But, Jan. Implementing the memory writes does not mean breakpoints
> automatically start to work!
It approximately should though.
> Yes, gdb writes cc, and yes the tracee reports SIGTRAP. But after
> that "continue" does nothing except "$c", and the tracee naturally
> gets SIGILL. I expected that, since ugdb doesn't even know the code
> was changed, gdb should write the original byte back before continue,
> but this doesn't happen.
In normal all-stop mode, gdb does normally replace the old
instruction, in order to single-step over it with the 's' packet.
Perhaps you're testing some buggy non-stop aspect that only works
with 'Z' breakpoint management packets? A fuller packet trace
would help explain.
- FChE
next prev parent reply other threads:[~2010-09-09 12:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 19:22 Oleg Nesterov
2010-09-09 10:29 ` Jan Kratochvil
2010-09-09 15:06 ` Oleg Nesterov
2010-09-09 12:39 ` Frank Ch. Eigler [this message]
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
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=y0my6bbccqs.fsf@fche.csb \
--to=fche@redhat.com \
--cc=archer@sourceware.org \
--cc=oleg@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).