From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] breakpoint remove fail handle bug fix
Date: Mon, 16 Apr 2012 10:01:00 -0000 [thread overview]
Message-ID: <20120416094950.GA10560@host2.jankratochvil.net> (raw)
In-Reply-To: <4F863B12.2040304@mentor.com>
On Thu, 12 Apr 2012 04:16:50 +0200, Hui Zhu wrote:
> But it didn't handle the issue when the target is remote.
So a similar fix is needed also for gdbserver, isn't it?
One needs to write a testcase for later check-in anyway, testing gdbserver
without the testcase/testsuite I find too painful.
I still do not see a reason to really handled failed breakpoint removal (or
insert), gdbserver also can access /proc/PID/mem etc., cannot it?
Thanks,
Jan
next prev parent reply other threads:[~2012-04-16 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 9:32 Hui Zhu
2012-04-11 10:53 ` Yao Qi
2012-04-11 21:33 ` Jan Kratochvil
2012-04-12 4:04 ` Hui Zhu
2012-04-16 10:01 ` Jan Kratochvil [this message]
2012-04-16 16:42 ` Hui Zhu
2012-04-17 21:15 ` Jan Kratochvil
2012-04-12 4:45 ` Doug Evans
2012-04-12 4:35 ` Doug Evans
2012-04-16 9:50 ` Hui Zhu
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=20120416094950.GA10560@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.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