From: Hui Zhu <teawater@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, palves@redhat.com, hui_zhu@mentor.com,
gdb-patches@sourceware.org, marc.khouzam@ericsson.com
Subject: Re: [PATCH] add -s option to make -break-insert support dprintf
Date: Mon, 20 May 2013 07:31:00 -0000 [thread overview]
Message-ID: <CANFwon2V92hrOOvum+g5o+AFKLwNn+PsrKtskjdWJBoq95H_vg@mail.gmail.com> (raw)
In-Reply-To: <CANFwon0fMc6efTtEVn_WLQ+8EaCzQ6f2AJH22jPg1RHyhnM2eg@mail.gmail.com>
Ping http://sourceware.org/ml/gdb-patches/2013-05/msg00460.html
Thanks,
Hui
On Tue, May 14, 2013 at 12:56 PM, Hui Zhu <teawater@gmail.com> wrote:
> On Mon, May 13, 2013 at 11:55 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>> From: Hui Zhu <teawater@gmail.com>
>>> Date: Mon, 13 May 2013 11:38:40 +0800
>>> Cc: tromey@redhat.com, palves@redhat.com, hui_zhu@mentor.com,
>>> gdb-patches@sourceware.org, marc.khouzam@ericsson.com
>>>
>>> >> +If @var{location} cannot be parsed (for example if it
>>> > ^
>>> > A comma is missing.
>>>
>>> The comma is after the right parenthesis: refers to unknown files or functions),
>>> Do I need change this part to following format?
>>> If @var{location} cannot be parsed, (for example if it
>>> refers to unknown files or functions) create a pending
>>
>> No, I meant the comma after "for example", inside the parentheses.
>
> Fixed.
>
> Post a new version for it.
>
> Thanks,
> Hui
>
> 2013-05-14 Hui Zhu <hui@codesourcery.com>
>
> * breakpoint.c (dprintf_breakpoint_ops): Remove its static.
> * breakpoint.h (dprintf_breakpoint_ops): Add extern.
> * mi/mi-cmd-break.c (ctype.h): New include.
> (gdb_obstack.h): New include.
> (mi_argv_to_format, mi_cmd_break_insert_1): New.
> (mi_cmd_break_insert): Call mi_cmd_break_insert_1.
> (mi_cmd_dprintf_insert): New.
> * mi/mi-cmds.c (mi_cmds): Add "dprintf-insert".
> * mi/mi-cmds.h (mi_cmd_dprintf_insert): New extern.
>
> 2013-05-14 Hui Zhu <hui@codesourcery.com>
>
> * gdb.texinfo (GDB/MI Breakpoint Commands): Describe the
> "-dprintf-insert" command.
>
> 2013-05-14 Hui Zhu <hui@codesourcery.com>
>
> * gdb.mi/Makefile.in (PROGS): Add "mi-dprintf".
> * gdb.mi/mi-dprintf.exp, gdb.mi/mi-dprintf.c: New.
next prev parent reply other threads:[~2013-05-20 7:31 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 17:44 Hui Zhu
2013-03-28 18:37 ` Eli Zaretskii
2013-03-29 16:12 ` Hui Zhu
2013-03-29 16:13 ` Eli Zaretskii
2013-04-09 23:31 ` Pedro Alves
2013-04-10 19:44 ` Marc Khouzam
2013-04-10 19:45 ` Pedro Alves
2013-04-11 6:15 ` Hui Zhu
2013-04-11 17:47 ` Pedro Alves
2013-04-12 14:56 ` Hui Zhu
2013-04-12 15:22 ` Pedro Alves
2013-04-15 18:59 ` Hui Zhu
2013-04-15 19:41 ` Pedro Alves
2013-04-16 9:31 ` Hui Zhu
2013-04-22 1:25 ` Yao Qi
2013-04-12 16:03 ` Eli Zaretskii
2013-04-13 14:16 ` Tom Tromey
2013-04-15 18:04 ` Hui Zhu
2013-04-15 19:36 ` Pedro Alves
2013-04-16 9:31 ` Hui Zhu
2013-04-22 0:18 ` Tom Tromey
2013-04-22 9:07 ` Hui Zhu
2013-04-25 6:51 ` Tom Tromey
2013-05-03 5:43 ` Hui Zhu
2013-05-07 20:50 ` Tom Tromey
2013-05-10 10:57 ` Hui Zhu
2013-05-10 15:24 ` Tom Tromey
2013-05-11 2:38 ` Hui Zhu
2013-05-11 7:29 ` Eli Zaretskii
2013-05-13 3:39 ` Hui Zhu
2013-05-13 15:55 ` Eli Zaretskii
2013-05-14 4:56 ` Hui Zhu
2013-05-20 7:31 ` Hui Zhu [this message]
2013-05-20 15:44 ` Eli Zaretskii
2013-05-21 4:25 ` Hui Zhu
2013-05-21 8:10 ` [patch] Fix racy FAILs due to "read1" [Re: [PATCH] add -s option to make -break-insert support dprintf] Jan Kratochvil
2013-05-21 9:30 ` Hui Zhu
2013-05-21 15:01 ` [commit] " Jan Kratochvil
2013-05-22 1:05 ` Hui Zhu
2013-05-23 14:03 ` [patch] Fix racy FAILs #2 " Jan Kratochvil
2013-05-24 15:37 ` [commit] " Jan Kratochvil
2013-05-27 11:02 ` Hui Zhu
2013-05-13 16:23 ` [PATCH] add -s option to make -break-insert support dprintf Tom Tromey
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=CANFwon2V92hrOOvum+g5o+AFKLwNn+PsrKtskjdWJBoq95H_vg@mail.gmail.com \
--to=teawater@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.com \
--cc=marc.khouzam@ericsson.com \
--cc=palves@redhat.com \
--cc=tromey@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