From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Cheung <mcheung63@hotmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Adding another debug protocol
Date: Wed, 14 Nov 2012 17:43:12 +0100 [thread overview]
Message-ID: <50A3CA20.4020205@siemens.com> (raw)
In-Reply-To: <BAY404-EAS198C7FB4BB2DB9648EDAFDEB5530@phx.gbl>
On 2012-11-14 17:28, Peter Cheung wrote:
> hi Jan, you are the maintainer of the gdb server of qemu?
Not formally. I'm heavily using it for kernel debugging for a couple of
years. Therefore, I'm fixing and enhancing it from time to time.
> I think if I can't create my debug protocol, it is not easy to adopt peter-bochs debugger to qemu, in peter-bochs, there are some features I think current gdb protocol doesn't care, such as profiling, kernel module monitoring, call graph history, real time address probeing.
> I know qemu is made by a lots of people, seems not easy to convince everyone.
A good general rule, not only in open source, is to at least try to fix
existing infrastructure. If that fails provably, you can come up with a
new version to replace or augment things.
E.g., you didn't explain yet why the gdb protocol and our existing stub
cannot be extended in a backward compatible way that allows your
debugger to attach to it. That way not only your debugger (is it Windows
hosted?) could benefit from the improvements but the whole (x86) gdb world.
Jan
PS: Please don't top-post, cite what you comment on.
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-11-14 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 10:45 [Qemu-devel] Adding another debug protocol Peter Cheung
2012-11-14 10:54 ` Peter Maydell
2012-11-14 14:40 ` Peter Cheung
2012-11-14 15:13 ` Jan Kiszka
2012-11-14 16:28 ` Peter Cheung
2012-11-14 16:43 ` Jan Kiszka [this message]
2012-11-15 1:58 ` Peter Cheung
2012-11-15 8:02 ` Jan Kiszka
2012-11-15 8:44 ` Peter Cheung
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=50A3CA20.4020205@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=mcheung63@hotmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).