Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [ob] unbreak MI
Date: Tue, 27 Nov 2007 07:00:00 -0000	[thread overview]
Message-ID: <200711271000.06151.ghost@cs.msu.su> (raw)
In-Reply-To: <18251.47321.156923.358334@kahikatea.snap.net.nz>

On Tuesday 27 November 2007 09:27:37 Nick Roberts wrote:
>  > > Generally, with a NULL pointer, or and address that can't be dereferenced,
>  > > MI prints out the value field as value="".
>  > > 
>  > > What is the problem in this case?  Why isn't the right fix to add a
>  > > check_typedef somewhere?
>  > 
>  > check_typedef? The original problem was that check_typedef was getting
>  > called on NULL pointer, so adding more check_typedef calls won't help.
>  > Probably:
>  > 
>  >         if (!gdb_type)
>  >                 ui_out_field_string (uiout, "value", "");
>  >         else if (mi_print_value_p (gdb_type, print_values))
>  >                 ui_out_field_string (uiout, "value", varobj_get_value (var));
>  > 
>  > is the right logic?
> 
> It's probably the right logic, but it seems to cure the symptom rather than the
> cause.  What I mean't, I guess, was where/how does check_typedef is get passed
> a NULL pointer?  And can't that call be conditioned (i.e. "add a *check* to
> check_typedef") , e.g., something like:
> 
> if (!gdb_type)
>    check_typedef (gdb_type)

Just look at mi_print_value_p, and you'll see a call to check_typedef. Actually,
the code previously looked like:

	if (type != NULL)
		type = check_typedef (type);

It was changed in revision 1.38, with the following comment:

	2007-08-28  Michael Snyder  <msnyder@access-company.com>

	* mi/mi-cmd-var.c (mi_print_value_p): No longer necessary to
	check for null before calling check_typedef.

However, apparently check_typedef still crashes when passed NULL,
and it can be passed NULL.

The original code, in fact, was in error too, because of this:

  return (TYPE_CODE (type) != TYPE_CODE_ARRAY
	  && TYPE_CODE (type) != TYPE_CODE_STRUCT
	  && TYPE_CODE (type) != TYPE_CODE_UNION);	

This will crash if 'type' is NULL. Testsuite fails to detect this because presently
type is NULL only for C++ pseudo-fields  ('public'/'private') and the code
above is only executed for --simple-values.

Does this clarify things?

- Volodya


  reply	other threads:[~2007-11-27  7:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 18:45 Vladimir Prus
2007-11-27  3:08 ` Nick Roberts
2007-11-27  6:17   ` Vladimir Prus
2007-11-27  6:28     ` Nick Roberts
2007-11-27  7:00       ` Vladimir Prus [this message]
2007-11-27 10:33         ` Nick Roberts
2007-11-27 10:45           ` Vladimir Prus
2007-11-27 11:08             ` Nick Roberts
2007-11-27 20:47         ` Michael Snyder
2007-11-27 21:05           ` Vladimir Prus
2007-11-27 23:13           ` Nick Roberts
2007-11-27 13:44   ` Daniel Jacobowitz
2007-11-27 23:11     ` Nick Roberts

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=200711271000.06151.ghost@cs.msu.su \
    --to=ghost@cs.msu.su \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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