Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Daniel Gutson <daniel.gutson@tallertechnologies.com>,
		gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Small segfault fix when there is no python
Date: Thu, 20 Mar 2014 17:52:00 -0000	[thread overview]
Message-ID: <CADPb22RLP_A7AFBsTkw_v62j54YCkZVaGPi3pLbg4Vjx2JPSRg@mail.gmail.com> (raw)
In-Reply-To: <m3pplgpyjb.fsf@redhat.com>

On Thu, Mar 20, 2014 at 10:31 AM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> On Thursday, March 20 2014, Daniel Gutson wrote:
>
>> Hi,
>>
>>    the small attached patch prevents gdb to segfault when an extension
>> language definition has no ops,
>> which e.g. occurs when HAVE_PYTHON is not defined so
>> extension_language_python remains with ops in NULL.
>> This causes the line
>>    if (extlang->ops->eval_from_control_command != NULL)
>> (in eval_ext_lang_from_control_command) to dereference a null pointer.
>
> Hi Daniel,
>
> Thanks for the patch.  This is a simple patch so it doesn't need a
> copyright assignment from you.  However, if you intend to continue
> contributing to GDB, please e-mail me offlist and I can send you the
> papers to obtain the assignment.
>
> Just a few comments about formatting issues.
>
>>     2014-03-20    Daniel Gutson (daniel.gutson@tallertechnologies.com)
>>
>> gdb/
>>     * extension.c: (eval_ext_lang_from_control_command) Added check to
>> prevent dereference of null pointer.
>
> The ChangeLog format is wrong.  Take a look at the ChangeLog file for
> lots of examples, but basically you need to write:
>
> 2014-03-20  Your Name  <your@email>
>
>         * file.c (function): Added check to prevent blabla...
>
> Pay attention to the 2 spaces between the date, the name and the e-mail,
> and also to the TAB character indenting the description.
>
>> diff --git a/gdb/extension.c b/gdb/extension.c
>> index c2f502b..8357ee8 100644
>> --- a/gdb/extension.c
>> +++ b/gdb/extension.c
>> @@ -342,11 +342,14 @@ eval_ext_lang_from_control_command (struct command_line *cmd)
>>      {
>>        if (extlang->cli_control_type == cmd->control_type)
>>       {
>> -       if (extlang->ops->eval_from_control_command != NULL)
>> -         {
>> -           extlang->ops->eval_from_control_command (extlang, cmd);
>> -           return;
>> -         }
>> +      if (extlang->ops != NULL)
>> +        {
>> +         if (extlang->ops->eval_from_control_command != NULL)
>> +           {
>> +             extlang->ops->eval_from_control_command (extlang, cmd);
>> +             return;
>> +           }
>> +        }
>
> You could simplify this by writing:
>
>   if (extlang->ops != NULL && extlang->ops->eval_from_control_command != NULL)
>
> If you don't want to join the two "if"s, then you don't need to put the
> braces on the outter "if", because it has one single statement.
>
> The patch looks good to me, but I'm not a maintainer and can't approve
> it.
>
> Thanks,
>
> --
> Sergio


I did an audit of all the uses of ->ops and think this is the only one I missed.
I will commit with the needed changes.
Thanks for the patch!


  reply	other threads:[~2014-03-20 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 16:33 Daniel Gutson
2014-03-20 17:31 ` Sergio Durigan Junior
2014-03-20 17:52   ` Doug Evans [this message]
2014-03-21 16:24     ` Daniel Gutson
2014-03-22  7:02       ` Doug Evans

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=CADPb22RLP_A7AFBsTkw_v62j54YCkZVaGPi3pLbg4Vjx2JPSRg@mail.gmail.com \
    --to=dje@google.com \
    --cc=daniel.gutson@tallertechnologies.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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