From: Joel Brobecker <brobecker@adacore.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Make tracepoints into breakpoints
Date: Mon, 30 Mar 2009 15:44:00 -0000 [thread overview]
Message-ID: <20090330153348.GY9472@adacore.com> (raw)
In-Reply-To: <49CD275B.1020003@codesourcery.com>
Hi Stan,
I was scanning your patch a little, to see waht you had needed to do
in order to do this transition. I noticed a few things - not sure how
important they are, given how quickly I looked at it. But there you go.
> *************** bpstat_what (bpstat bs)
> *** 3324,3329 ****
> --- 3358,3367 ----
> bs_class = bp_silent;
> retval.call_dummy = 1;
> break;
> +
> + case bp_tracepoint:
> + /* (should never occur, complain about it) */
> + continue;
> }
> current_action = table[(int) bs_class][(int) current_action];
> }
This hunk looks really strange... Out of place?
The thing that caught my attention too was the comment that seem
to imply that this is a temporary comment, almost a FIXME. Not sure
if this is the case, but the complaint is not there (elsewhere maybe?).
> + /* Remove a tracepoint (or all if no argument) */
Nit-picking on the missing period at the end of your sentence. I just
happened to notice it, but I haven't really checked the rest.
> + #if 0 /* names of commands not visible here, not clear if worth fixing */
> + if (cmd_cfunc_eq (cmd, while_stepping_pseudocommand))
> + indent = i2;
> + else if (cmd_cfunc_eq (cmd, end_actions_pseudocommand))
> + indent = i1;
> + #endif
Do we really want to keep this #if 0? I'd personally rather have
a comment.
I'd also like to look at your patch again sometime soon, to figure out
whether it'd make sense or not for tracepoints to have their own
breakpoint_ops routines... To be continued :)
--
Joel
next prev parent reply other threads:[~2009-03-30 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 19:57 Stan Shebs
2009-03-28 9:07 ` Eli Zaretskii
2009-03-30 16:10 ` Stan Shebs
2009-03-28 18:11 ` Eli Zaretskii
2009-03-30 15:44 ` Joel Brobecker [this message]
2009-03-30 16:56 ` Joel Brobecker
2009-03-30 18:29 ` Stan Shebs
2009-03-30 22:21 ` Joel Brobecker
2009-03-30 23:01 ` Stan Shebs
2009-03-30 22:07 ` Stan Shebs
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=20090330153348.GY9472@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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