From: fche@redhat.com (Frank Ch. Eigler)
To: Oleg Nesterov <oleg@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
utrace-devel@redhat.com, archer@sourceware.org
Subject: Re: gdbstub initial code, v8
Date: Tue, 07 Sep 2010 02:59:00 -0000 [thread overview]
Message-ID: <y0mr5h6xnqe.fsf@fche.csb> (raw)
In-Reply-To: <20100906204446.GA29925@redhat.com> (Oleg Nesterov's message of "Mon, 6 Sep 2010 22:44:46 +0200")
Oleg Nesterov <oleg@redhat.com> writes:
> [...]
>> Therefore until you track some ugdb-specific software(*)
>> breakpoints ugdb does not need to support Z0 IMO. I guess ugdb
>> will never have to support these: thread-related(?) and tracepoint
>> ones.
> Good! I thought ugdb should somehow handle this all "transparently"
> for gdb. I thought (I don't know why) that writing "int 3" from gdb
> side should be avoided in favour of some "better" method unknown to me.
Please note that last year's gdbstub prototype used kernel uprobes as
an optional gdb breakpoint implementation (i.e., a backend for the Z
packets). When/if the lkml uprobes patches actually get merged, ugdb
should also use them.
- FChE
next prev parent reply other threads:[~2010-09-07 2:59 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
2010-09-06 18:31 ` Jan Kratochvil
2010-09-06 20:48 ` Oleg Nesterov
2010-09-07 2:59 ` Frank Ch. Eigler [this message]
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=y0mr5h6xnqe.fsf@fche.csb \
--to=fche@redhat.com \
--cc=archer@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--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).