Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,  Tom Tromey <tom@tromey.com>,
	 "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] PR python/18565 - make Frame.function work for inline frames
Date: Mon, 25 Jul 2016 15:01:00 -0000	[thread overview]
Message-ID: <87bn1lu5h9.fsf@tromey.com> (raw)
In-Reply-To: <d861e87d-a94d-5ae9-5d51-3f7f8ad0ccc1@redhat.com> (Pedro Alves's	message of "Mon, 25 Jul 2016 12:04:16 +0100")

Yao> The reason I suggested that way is that the exception may be thrown
Yao> out in find_frame_funname after the memory is allocated for
Yao> funname, so we need xfree in CATCH, and also need xfree afterwards.

Pedro> I disagree.  In general, I think that up until the called function does a normal
Pedro> return, the memory for output parameters is owned by the called function.
Pedro> A normal return then transfers ownership of the output parameters' memory
Pedro> to the caller.

Pedro> So I think that it's find_frame_funname that should be responsible for making
Pedro> sure that memory for output parameters is cleaned up on exception, or be
Pedro> written in a way that never throws after the memory allocation, which it may be
Pedro> already, but I haven't checked in detail.

I agree with this.

I've just looked into the function and its callers.

Most cases in find_frame_funname clearly set *funname in a spot where an
exception cannot occur.  The one iffy case is:

	  *funname = xstrdup (SYMBOL_PRINT_NAME (func));
[...]
	  if (*funlang == language_cplus)
	    {
	      /* It seems appropriate to use SYMBOL_PRINT_NAME() here,
		 to display the demangled name that we already have
		 stored in the symbol table, but we stored a version
		 with DMGL_PARAMS turned on, and here we don't want to
		 display parameters.  So remove the parameters.  */
	      char *func_only = cp_remove_params (*funname);

I'm not 100% sure that cp_remove_params cannot throw.  However, it's
simple to deal with this by adding a cleanup in find_frame_funname.  I'm
happy to do this if desired.

Another approach might be to have a free_current_contents cleanup at the
start of find_frame_funname and discard it at the exit.  This would
maybe make it a bit safer in the face of future changes.

Alternatively, if we need a try/catch in the caller to possibly free the
function name, then several other callers are incorrect (ada-lang.c and
stack.c).

Tom


  reply	other threads:[~2016-07-25 15:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 16:11 Tom Tromey
     [not found] ` <86ziqfq6sz.fsf@gmail.com>
2016-06-22 18:43   ` Tom Tromey
2016-07-25 10:23     ` Yao Qi
2016-07-25 11:04       ` Pedro Alves
2016-07-25 15:01         ` Tom Tromey [this message]
2016-07-26 11:14           ` Pedro Alves
2016-07-26 13:18             ` Tom Tromey
2016-07-26 14:33               ` Pedro Alves
2016-08-03  8:15             ` Yao Qi
2016-08-03 15:14               ` Tom Tromey
2016-08-03 17:57                 ` Pedro Alves
2016-08-03  8:07         ` Yao Qi
2016-08-03 11:35           ` Pedro Alves
2016-08-03 13:15             ` 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=87bn1lu5h9.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=qiyaoltc@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