Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>
Subject: Re: [commit] py-prettyprint.c, val may be null
Date: Tue, 01 Mar 2011 21:24:00 -0000	[thread overview]
Message-ID: <201103012124.33473.pedro@codesourcery.com> (raw)
In-Reply-To: <4D6D5F71.5040802@vmware.com>

On Tuesday 01 March 2011 21:04:49, Michael Snyder wrote:
>   2011-03-01  Michael Snyder  <msnyder@vmware.com>
> 
>         * python/py-prettyprint.c (apply_val_pretty_printer): VAL may
>         be null.

How?  I think it could a while ago, but not anymore.  I've recently
made sure val_print always gets a non-NULL value, and we'd now
crash elsewhere otherwise.

-- 
Pedro Alves

> 
> Index: python/py-prettyprint.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/python/py-prettyprint.c,v
> retrieving revision 1.21
> diff -u -p -u -p -r1.21 py-prettyprint.c
> --- python/py-prettyprint.c     14 Feb 2011 11:10:53 -0000      1.21
> +++ python/py-prettyprint.c     1 Mar 2011 21:02:05 -0000
> @@ -692,7 +692,8 @@ apply_val_pretty_printer (struct type *t
>    enum string_repr_result print_result;
>  
>    /* No pretty-printer support for unavailable values.  */
> -  if (!value_bytes_available (val, embedded_offset, TYPE_LENGTH (type)))
> +  if (val && !value_bytes_available (val, embedded_offset, 
> +                                    TYPE_LENGTH (type)))
>      return 0;
>  


  reply	other threads:[~2011-03-01 21:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01 21:04 Michael Snyder
2011-03-01 21:24 ` Pedro Alves [this message]
2011-03-01 21:41   ` Michael Snyder
2011-03-01 21:46     ` Pedro Alves
2011-03-01 21:55       ` Michael Snyder

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=201103012124.33473.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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