Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Robert Norton <rnorton@broadcom.com>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb@sourceware.org
Subject: Re: Segfault in varobj.c
Date: Fri, 27 Jul 2007 14:30:00 -0000	[thread overview]
Message-ID: <20070727130730.GA27227@caradoc.them.org> (raw)
In-Reply-To: <B0D822BFECD50F4991F2516EA50F273C01FEB544@NT-IRVA-0752.brcm.ad.broadcom.com>

On Fri, Jul 27, 2007 at 05:52:25AM -0700, Robert Norton wrote:
> Breakpointing in c_type_of_child (now c_describe_child) we end up in the
> default case of the switch because the parent has type code
> TYPE_CODE_TYPEDEF, so could it be that the switch requires another case
> to handle this situation? I'll see if I can come up with a minimal test
> binary based on this.

No, that won't happen any more.  See get_value_type.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2007-07-27 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 11:51 Robert Norton
2007-07-27 12:03 ` Nick Roberts
2007-07-27 12:16   ` Robert Norton
2007-07-27 12:52     ` Nick Roberts
2007-07-27 13:07       ` Robert Norton
2007-07-27 14:30         ` Daniel Jacobowitz [this message]

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=20070727130730.GA27227@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=nickrob@snap.net.nz \
    --cc=rnorton@broadcom.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