From: Hui Zhu <hui_zhu@mentor.com>
To: Doug Evans <xdje42@gmail.com>
Cc: Pedro Alves <palves@redhat.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Let gdbserver doesn't tell GDB it support target-side breakpoint conditions and commands if it doesn't support 'Z' packet
Date: Sun, 08 Dec 2013 14:18:00 -0000 [thread overview]
Message-ID: <52A47FB9.2030407@mentor.com> (raw)
In-Reply-To: <CAP9bCMT7NfYrUe3ie1rVtSt1nv9Mh0m0y-YtQm2pJt5YOGCfYA@mail.gmail.com>
On 12/08/13 16:34, Doug Evans wrote:
> On Sat, Dec 7, 2013 at 9:13 PM, Hui Zhu <hui_zhu@mentor.com> wrote:
>> 2013-12-08 Hui Zhu <hui@codesourcery.com>
>>
>> PR gdb/16101
>> * breakpoint.c (insert_bp_location): Change hw_bp_err_string to
>> bp_err_string.
>>
>> Output error message of software breakpoints.
>> Make solib error message output use same code with hardware
>> breakpoints and software breakpoints.
>>
>> * remote.c (remote_insert_breakpoint): If this breakpoint has
>> target-side commands but this stub doesn't support Z0 packets,
>> throw error.
>
> Nit. This changelog is badly formatted.
> Please fix.
>
> I suspect, though this is only based on perusal of the patch,
> and not close analysis, that you meant to write:
>
> PR gdb/16101
> * breakpoint.c (insert_bp_location): Change hw_bp_err_string to
> bp_err_string. Output error message of software breakpoints.
> Make solib error message output use same code with hardware
> breakpoints and software breakpoints.
>
> * remote.c (remote_insert_breakpoint): If this breakpoint has
> target-side commands but this stub doesn't support Z0 packets,
> throw error.
>
Thanks for your remind.
2013-12-08 Hui Zhu <hui@codesourcery.com>
PR gdb/16101
* breakpoint.c (insert_bp_location): Change hw_bp_err_string to
bp_err_string. Output error message of software breakpoints.
Make solib error message output use same code with hardware
breakpoints and software breakpoints.
* remote.c (remote_insert_breakpoint): If this breakpoint has
target-side commands but this stub doesn't support Z0 packets,
throw error.
> [I may have gotten the indentation wrong, cut-n-paste in gmail, blech.
> The point is the blank line before "Output error ..." is wrong. ISTM.]
>
I got some indentation issue with web gmail in a few weeks ago.
But this time it looks OK in my part. I think they has fixed the issue.
Thanks,
Hui
next prev parent reply other threads:[~2013-12-08 14:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 10:30 Hui Zhu
2013-10-21 15:37 ` Pedro Alves
2013-11-28 10:56 ` Hui Zhu
2013-11-28 17:38 ` Maciej W. Rozycki
2013-11-29 9:41 ` Hui Zhu
2013-11-29 15:27 ` [pushed] Plug target side conditions and commands leaks (was: Re: [PATCH] Let gdbserver doesn't tell GDB it support target-side breakpoint conditions and commands if it doesn't support 'Z' packet) Pedro Alves
2013-11-29 16:05 ` [PATCH] Let gdbserver doesn't tell GDB it support target-side breakpoint conditions and commands if it doesn't support 'Z' packet Pedro Alves
2013-12-02 12:45 ` Hui Zhu
2013-12-02 14:38 ` Pedro Alves
2013-12-03 4:50 ` Hui Zhu
2013-12-03 4:54 ` Hui Zhu
2013-12-06 19:29 ` Pedro Alves
2013-12-08 5:19 ` Hui Zhu
2013-12-08 8:34 ` Doug Evans
2013-12-08 14:18 ` Hui Zhu [this message]
2013-12-09 19:48 ` Pedro Alves
2013-12-09 21:07 ` Doug Evans
2013-12-10 17:34 ` Pedro Alves
2013-12-10 18:14 ` [PATCH] Eliminate UNSUPPORTED_ERROR Pedro Alves
2013-12-11 16:33 ` Doug Evans
2013-12-11 19:17 ` Pedro Alves
2013-12-12 4:23 ` Doug Evans
2013-12-12 10:23 ` Pedro Alves
2013-12-11 16:40 ` [PATCH] Let gdbserver doesn't tell GDB it support target-side breakpoint conditions and commands if it doesn't support 'Z' packet Doug Evans
2013-12-12 10:55 ` breakpoint.c:insert_bp_location: Constify local. (was: Re: [PATCH] Let gdbserver doesn't tell GDB it support target-side breakpoint conditions and commands if it doesn't support 'Z' packet) Pedro Alves
2013-12-12 12:55 ` [PATCH] Let gdbserver doesn't tell GDB it support target-side breakpoint conditions and commands if it doesn't support 'Z' packet Pedro Alves
2014-01-09 18:36 ` Pedro Alves
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=52A47FB9.2030407@mentor.com \
--to=hui_zhu@mentor.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=xdje42@gmail.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