From: Joel Brobecker <brobecker@adacore.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Michael Snyder <msnyder@vmware.com>,
shuchang zhou <shuchang.zhou@gmail.com>,
paawan oza <paawan1982@yahoo.com>,
Tom Tromey <tromey@redhat.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFC] Add support of software single step to process record
Date: Wed, 23 Dec 2009 06:52:00 -0000 [thread overview]
Message-ID: <20091223065141.GT2788@adacore.com> (raw)
In-Reply-To: <daef60380912222238h6702aecfp3e13a467cbe46cb0@mail.gmail.com>
> Joel, I remove the current_gdbarch() from this patch, but for
> get_current_frame, I cannot find any function that fit for replace it.
> Could you help me with it?
Upon further investigation, I believe that this is the only way to do
this. I don't think you can get the frame from the arguments provided
to "resume". I did a quick research and infrun.c:resume does the same
thing (actually, it's maybe_software_singlestep).
> + if (single_step_breakpoints[0] != NULL
> + || single_step_breakpoints[1] != NULL)
> + return 1;
> +
> + return 0;
Style nit: You really don't have to fix this, as this is a matter of
style more than correctness, but we usually write the above code as
return (single_step_breakpoints[0] != NULL
|| single_step_breakpoints[1] != NULL)
This avoids the type of mistake you made. I tend to like the style
you used when there are several consecutive if conditions that allow
me to return early (a type of soft assert), or to avoid unreasonable
nesting levels.
--
Joel
next prev parent reply other threads:[~2009-12-23 6:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 8:21 Hui Zhu
2009-12-18 19:37 ` Michael Snyder
2009-12-20 13:48 ` Joel Brobecker
2009-12-23 6:38 ` Hui Zhu
2009-12-23 6:52 ` Joel Brobecker [this message]
2009-12-23 9:24 ` Hui Zhu
[not found] ` <8d62b6fe0912231751p1202294cw83430e8d53af0951@mail.gmail.com>
2009-12-24 1:54 ` Fwd: " shuchang zhou
2009-12-24 17:38 ` Pedro Alves
2010-01-04 14:23 ` Hui Zhu
2010-01-08 16:24 ` Pedro Alves
2010-05-25 5:14 ` Hui Zhu
2010-05-27 6:51 ` Hui Zhu
2010-06-11 13:55 ` Pedro Alves
2010-06-20 7:29 ` Hui Zhu
2010-06-22 10:13 ` Pedro Alves
2010-07-19 7:58 ` Hui Zhu
2009-12-22 18:23 ` Tom Tromey
2009-12-23 3:09 ` 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=20091223065141.GT2788@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=paawan1982@yahoo.com \
--cc=shuchang.zhou@gmail.com \
--cc=teawater@gmail.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