From: Pedro Alves <palves@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Keith Seitz <keiths@redhat.com>, Hui Zhu <hui_zhu@mentor.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix dprintf work not right if it is pending
Date: Tue, 09 Apr 2013 15:28:00 -0000 [thread overview]
Message-ID: <51640391.2040801@redhat.com> (raw)
In-Reply-To: <CANFwon3rTwU1AkmeWAoHJZLH=DFrwMzbazK06M5UgBbSn7ZJ2A@mail.gmail.com>
Hi Hui,
On 04/09/2013 10:00 AM, Hui Zhu wrote:
> On Mon, Apr 8, 2013 at 10:39 PM, Pedro Alves <palves@redhat.com> wrote:
>>
>>> +set testfile "dprintf-pending"
>>> +set libfile "dprintf-pendshr"
>>> +set srcfile $testfile.c
>>> +set libsrc $srcdir/$subdir/$libfile.c
>>> +set binfile $objdir/$subdir/$testfile
>>> +set lib_sl $objdir/$subdir/$libfile.sl
>>
>> Please use standard_testfile/standard_output_file.
>
> Fixed.
Close, but:
> +standard_testfile .c
> +set libfile "dprintf-pendshr"
> +set libsrc $srcdir/$subdir/$libfile.c
> +set lib_sl $objdir/$subdir/$libfile.sl
".c" is not necessary. Do use standard_output_file please.
Like so:
standard_testfile
set libfile "dprintf-pendshr"
set libsrc $srcdir/$subdir/$libfile.c
set lib_sl [standard_output_file $libfile.sl]
Oh,
> +++ b/gdb/breakpoint.c
> @@ -12963,6 +12963,35 @@ bkpt_re_set (struct breakpoint *b)
> breakpoint_re_set_default (b);
> }
>
> +/* Dprintf breakpoint_ops methods. */
> +
> +static void
> +dprintf_re_set (struct breakpoint *b)
> +{
...
> +}
> +
> static int
> bkpt_insert_location (struct bp_location *bl)
> {
I only now noticed you're putting the new dprintf_re_set
function right in the middle of the
/* Default breakpoint_ops methods. */
bkpt_re_set (struct breakpoint *b)
...
bkpt_insert_location (struct bp_location *bl)
...
bkpt_remove_location (struct bp_location *bl)
...
bkpt_breakpoint_hit (const struct bp_location *bl,
...
bkpt_resources_needed (const struct bp_location *bl)
...
bkpt_print_it (bpstat bs)
...
bkpt_print_mention (struct breakpoint *b)
...
bkpt_decode_linespec (struct breakpoint *b, char **s,
...
section. If you keep scrolling down, you'll notice that
we have a section/block/group of functions for each
breakpoint type.
/* Virtual table for internal breakpoints. */
/* Virtual table for momentary breakpoints */
/* Specific methods for probe breakpoints. */
/* The breakpoint_ops structure to be used in tracepoints. */
etc. for all other types. Please don't break this layout.
Otherwise OK.
Thanks,
--
Pedro Alves
next prev parent reply other threads:[~2013-04-09 12:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 7:39 Hui Zhu
2013-03-22 12:40 ` Yao Qi
2013-03-25 1:00 ` Keith Seitz
2013-03-25 2:14 ` Yao Qi
2013-03-26 14:55 ` Hui Zhu
2013-03-28 17:07 ` Keith Seitz
2013-03-29 15:50 ` Hui Zhu
2013-04-03 3:34 ` Keith Seitz
2013-04-04 18:42 ` Hui Zhu
2013-04-05 18:30 ` Pedro Alves
2013-04-08 7:20 ` Keith Seitz
2013-04-08 17:57 ` Pedro Alves
2013-04-08 9:34 ` Hui Zhu
2013-04-08 14:35 ` Hui Zhu
2013-04-08 18:34 ` Pedro Alves
2013-04-09 15:28 ` Hui Zhu
2013-04-09 15:28 ` Pedro Alves [this message]
2013-04-10 15:57 ` Hui Zhu
2013-04-10 16:12 ` Hui Zhu
2013-04-11 5:46 ` Joel Brobecker
2013-04-11 17:03 ` Pedro Alves
2013-04-12 12:21 ` Hui Zhu
2013-03-25 8:25 ` Hui Zhu
2013-03-25 8:28 ` Yao Qi
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=51640391.2040801@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.com \
--cc=keiths@redhat.com \
--cc=teawater@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