From: "Robert Norton" <rnorton@broadcom.com>
To: "Nick Roberts" <nickrob@snap.net.nz>
Cc: gdb@sourceware.org
Subject: RE: FW: Segfault in varobj.c
Date: Mon, 30 Jul 2007 11:43:00 -0000 [thread overview]
Message-ID: <B0D822BFECD50F4991F2516EA50F273C020E382E@NT-IRVA-0752.brcm.ad.broadcom.com> (raw)
In-Reply-To: <18090.40609.505683.775495@kahikatea.snap.net.nz>
> -----Original Message-----
> From: Nick Roberts [mailto:nickrob@snap.net.nz]
> Sent: 28 July 2007 02:41
> To: Robert Norton
> Cc: gdb@sourceware.org
> Subject: Re: FW: Segfault in varobj.c
>
> Your example crashes with GDB 6.6 for me in the way you first
> reported.
Interesting! I think I needed an array of teststructs in the end.
Another one for the test suite?
> > Suppose I'll just have to go with a workaround until such
> time as we can
> > upgrade.
>
> Yes. It appears to be fixed in current CVS but isn't handled
> by GDB 6.6.
OK. I managed to avoid the segfault by backporting get_value_type and
changing the line
switch (TYPE_CODE (parent->type))
In c_type_of_child to
switch (TYPE_CODE (get_value_type(parent)))
This is still not right since the pointer fields which previously caused
a crash can now be expanded twice in eclipse. It seems gdb gets the type
of the child of the pointer wrong (it thinks it is still a pointer) and
allows it to be expanded again, but at least it doesn't crash!
Thanks for your assistance,
Robert
> --
> Nick
> http://www.inet.net.nz/~nickrob
>
>
prev parent reply other threads:[~2007-07-30 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 17:53 Robert Norton
2007-07-28 20:57 ` Nick Roberts
2007-07-30 11:43 ` Robert Norton [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=B0D822BFECD50F4991F2516EA50F273C020E382E@NT-IRVA-0752.brcm.ad.broadcom.com \
--to=rnorton@broadcom.com \
--cc=gdb@sourceware.org \
--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