Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <hui_zhu@mentor.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] breakpoint remove fail handle bug fix
Date: Mon, 16 Apr 2012 16:42:00 -0000	[thread overview]
Message-ID: <4F8C418C.80509@mentor.com> (raw)
In-Reply-To: <20120416094950.GA10560@host2.jankratochvil.net>

On 04/16/12 17:49, Jan Kratochvil wrote:
> 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

I just try to handle this issue for current issue or other issue about 
breakpoint in the future for example that a remote target cannot delete 
breakpoint when the inferior is running.  But I am OK if you think it is 
not very important.

I suggest we can doc clear about this part for the gdbserver developer.

Thanks,
Hui


  reply	other threads:[~2012-04-16 15:58 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
2012-04-16 16:42       ` Hui Zhu [this message]
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=4F8C418C.80509@mentor.com \
    --to=hui_zhu@mentor.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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