From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Remove a cleanup from scm-frame.c
Date: Sun, 22 Apr 2018 14:21:00 -0000 [thread overview]
Message-ID: <43a02241b2a0b1178a6dd8dfbd2ad581@polymtl.ca> (raw)
In-Reply-To: <20180421223936.31584-1-tom@tromey.com>
On 2018-04-21 18:39, Tom Tromey wrote:
> This removes a cleanup from scm-frame.c, replacing it with
> unique_xmalloc_ptr and a new scope. I believe this also fixes a
> latent bug involving calling do_cleanups twice for a single cleanup.
>
> Regression tested using the gdb.guile test suite on x86-64 Fedora 26.
>
> ChangeLog
> 2018-04-21 Tom Tromey <tom@tromey.com>
>
> * guile/scm-frame.c (gdbscm_frame_read_var): Use
> gdb::unique_xmalloc_ptr.
> ---
> gdb/ChangeLog | 5 +++++
> gdb/guile/scm-frame.c | 54
> ++++++++++++++++++++++++---------------------------
> 2 files changed, 30 insertions(+), 29 deletions(-)
>
> diff --git a/gdb/guile/scm-frame.c b/gdb/guile/scm-frame.c
> index 4f4766aceb..7b539677ff 100644
> --- a/gdb/guile/scm-frame.c
> +++ b/gdb/guile/scm-frame.c
> @@ -877,7 +877,6 @@ gdbscm_frame_read_var (SCM self, SCM symbol_scm,
> SCM rest)
> }
> else if (scm_is_string (symbol_scm))
> {
> - char *var_name;
> const struct block *block = NULL;
> struct cleanup *cleanup;
> struct gdb_exception except = exception_none;
> @@ -893,38 +892,35 @@ gdbscm_frame_read_var (SCM self, SCM symbol_scm,
> SCM rest)
> gdbscm_throw (except_scm);
> }
>
> - var_name = gdbscm_scm_to_c_string (symbol_scm);
> - cleanup = make_cleanup (xfree, var_name);
> - /* N.B. Between here and the call to do_cleanups, don't do
> anything
> - to cause a Scheme exception without performing the cleanup. */
> + {
> + gdb::unique_xmalloc_ptr<char> var_name
> + (gdbscm_scm_to_c_string (symbol_scm));
> + /* N.B. Between here and the end of the scope, don't do anything
> + to cause a Scheme exception. */
> +
> + TRY
> + {
> + struct block_symbol lookup_sym;
> +
> + if (block == NULL)
> + block = get_frame_block (frame, NULL);
> + lookup_sym = lookup_symbol (var_name.get (), block, VAR_DOMAIN,
> + NULL);
> + var = lookup_sym.symbol;
> + block = lookup_sym.block;
> + }
> + CATCH (ex, RETURN_MASK_ALL)
> + {
> + except = ex;
> + }
> + END_CATCH
> + }
>
> - TRY
> - {
> - struct block_symbol lookup_sym;
> -
> - if (block == NULL)
> - block = get_frame_block (frame, NULL);
> - lookup_sym = lookup_symbol (var_name, block, VAR_DOMAIN, NULL);
> - var = lookup_sym.symbol;
> - block = lookup_sym.block;
> - }
> - CATCH (ex, RETURN_MASK_ALL)
> - {
> - except = ex;
> - }
> - END_CATCH
> -
> - do_cleanups (cleanup);
> GDBSCM_HANDLE_GDB_EXCEPTION (except);
>
> if (var == NULL)
> - {
> - do_cleanups (cleanup);
> - gdbscm_out_of_range_error (FUNC_NAME, 0, symbol_scm,
> - _("variable not found"));
> - }
> -
> - do_cleanups (cleanup);
> + gdbscm_out_of_range_error (FUNC_NAME, 0, symbol_scm,
> + _("variable not found"));
> }
> else
> {
This looks good to me at first glance. Do you know if scm exceptions
(scm_throw) play well with C++, the destructors of the objects in the
exited scopes will correctly be called?
Simon
next prev parent reply other threads:[~2018-04-22 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 22:39 Tom Tromey
2018-04-22 14:21 ` Simon Marchi [this message]
2018-04-22 23:47 ` Tom Tromey
2018-04-23 1:40 Simon Marchi
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=43a02241b2a0b1178a6dd8dfbd2ad581@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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