From: Kevin Buettner <kevinb@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] infcmd.c: Don't attempt to record a NULL value after a finish command
Date: Wed, 30 Sep 2015 12:17:00 -0000 [thread overview]
Message-ID: <20150930051736.457e072c@pinnacle.lan> (raw)
In-Reply-To: <560BB90D.70905@redhat.com>
On Wed, 30 Sep 2015 11:27:25 +0100
Pedro Alves <palves@redhat.com> wrote:
> On 09/30/2015 05:43 AM, Kevin Buettner wrote:
> > Architectures which use RETURN_VALUE_STRUCT_CONVENTION will have a
> > NULL return value after executing a finish command. See get_return_value()
> > in infcmd.c.
> >
> > This patch avoids an eventual SIGSEV (caused by attempting to
> > derefrence a NULL pointer) by adding a suitable test to
> > finish_command_fsm_should_stop().
> >
> > I encountered this problem while testing msp430:
> >
> > (gdb) PASS: gdb.base/structs.exp: zed L<n> for finish; return 1 structs-tc
> > finish
> > Run till exit from #0 fun1 () at /ironwood1/sourceware-git/msp430-elf/../binutils-gdb/gdb/testsuite/gdb.base/structs.c:125
> > ERROR: Process no longer exists
> >
> > gdb/ChangeLog:
> > * infcmd.c (finish_command_fsm_should_stop): Don't attempt to
> > record a NULL value.
> > ---
> > gdb/infcmd.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/gdb/infcmd.c b/gdb/infcmd.c
> > index c4d7d8b..6be95e4 100644
> > --- a/gdb/infcmd.c
> > +++ b/gdb/infcmd.c
> > @@ -1788,7 +1788,7 @@ finish_command_fsm_should_stop (struct thread_fsm *self)
> > internal_error (__FILE__, __LINE__,
> > _("finish_command: function has no target type"));
> >
> > - if (TYPE_CODE (rv->type) != TYPE_CODE_VOID)
> > + if (rv->value != NULL && TYPE_CODE (rv->type) != TYPE_CODE_VOID)
> > {
> > struct value *func;
>
> It's this else block that below sets rv->value in the first place:
>
> if (TYPE_CODE (rv->type) != TYPE_CODE_VOID)
> {
> struct value *func;
>
> func = read_var_value (f->function, NULL, get_current_frame ());
> rv->value = get_return_value (func, rv->type);
> rv->value_history_index = record_latest_value (rv->value);
> }
>
> So seems like that patch would break !RETURN_VALUE_STRUCT_CONVENTION
> targets?
>
> I assume that it's record_latest_value that crashes? Isn't the right
> fix instead:
>
> rv->value = get_return_value (func, rv->type);
> - rv->value_history_index = record_latest_value (rv->value);
> + if (rv->value != NULL)
> + rv->value_history_index = record_latest_value (rv->value);
>
You're right. (I honestly don't know what I was thinking.)
Please commit your patch instead.
Thanks,
Kevin
next prev parent reply other threads:[~2015-09-30 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 4:43 Kevin Buettner
2015-09-30 10:27 ` Pedro Alves
2015-09-30 12:17 ` Kevin Buettner [this message]
2015-09-30 12:21 ` Pedro Alves
2015-09-30 13:02 ` Kevin Buettner
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=20150930051736.457e072c@pinnacle.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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