From: Oleg Nesterov <oleg@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: archer@sourceware.org, utrace-devel@redhat.com
Subject: Re: gdbstub initial code, v8
Date: Mon, 06 Sep 2010 18:21:00 -0000 [thread overview]
Message-ID: <20100906181808.GA22839@redhat.com> (raw)
In-Reply-To: <20100905194101.GA31584@host1.dyn.jankratochvil.net>
On 09/05, Jan Kratochvil wrote:
>
> On Sat, 04 Sep 2010 00:40:47 +0200, Oleg Nesterov wrote:
> > - implement qXfer:siginfo:read
> >
> > - implement continue with signal.
>
> OK, thanks, just it was a bit premature to ask for it I see. I miss at least
> memory writes
Yes. This is simple.
> (also to put in breakpoints):
And this is not clear to me, I need your help ;)
What should ugdb know about breakpoints? I played with the real
gdbserver, and afaics gdb just changes the tracee's memory and
inserts 0xcc (int 3). But gdb.info mentions "Z TYPE,ADDR,KIND"
packets.
So, what should ugdb do? Just implement memory write (M or X)
and then report SIGTRAP like gdbserver does?
Oleg.
next prev parent reply other threads:[~2010-09-06 18:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 22:44 Oleg Nesterov
2010-09-05 19:41 ` Jan Kratochvil
2010-09-06 18:21 ` Oleg Nesterov [this message]
2010-09-06 18:31 ` Jan Kratochvil
2010-09-06 20:48 ` Oleg Nesterov
2010-09-07 2:59 ` Frank Ch. Eigler
2010-09-08 19:24 ` Oleg Nesterov
2010-09-10 10:02 ` Roland McGrath
2010-09-06 18:27 ` gdbstub initial code, v8 && ptrace Oleg Nesterov
2010-09-06 19:45 ` Oleg Nesterov
2010-09-06 21:02 ` Oleg Nesterov
2010-09-10 10:10 ` Roland McGrath
2010-09-10 19:10 ` Oleg Nesterov
2010-10-13 7:14 ` Roland McGrath
2010-10-15 13:57 ` 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=20100906181808.GA22839@redhat.com \
--to=oleg@redhat.com \
--cc=archer@sourceware.org \
--cc=jan.kratochvil@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).