Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@cgsoftware.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: <jason@redhat.com>, <bkoz@redhat.com>, <libstdc++@gcc.gnu.org>,
	<gdb@sources.redhat.com>
Subject: Re: c++ debugging hosed
Date: Mon, 12 Nov 2001 11:29:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0111251133290.24550-100000@www.cgsoftware.com> (raw)
In-Reply-To: <200111250923.LAA04147@is.elta.co.il>



On Sun, 25 Nov 2001, Eli Zaretskii wrote:

> > From: Jason Merrill <jason@redhat.com>
> > Date: Wed, 14 Nov 2001 16:02:11 +0000
> >
> > > --with-dwarf2:
> > > (gdb) p *this
> > > can't find class named `std::basic_filebuf<char, std::char_traits<char> >', as given by C++ RTTI
> >
> > > default:
> > > (gdb) p *this
> > > Attempt to take contents of a non-pointer value.
> >
> > > Sadly, this bug has been around for 2 weeks now. It's making debugging
> > > C++ code more difficult than it should be. Any hope for a quick fix?
> >
> > I just updated my gdb for the first time in months and ran into the same
> > problem.  Looks like the V3 ABI support code isn't ready for prime time.
> > Until it is, you can disable it with this patch:
> >
> > *** gnu-v3-abi.c.~1~	Wed Nov 14 12:33:51 2001
> > --- gnu-v3-abi.c	Wed Nov 14 15:59:39 2001
> > *************** init_gnuv3_ops (void)
> > *** 349,355 ****
> > --- 360,368 ----
> >   void
> >   _initialize_gnu_v3_abi (void)
> >   {
> > + #if 0
> >     init_gnuv3_ops ();
> >
> >     register_cp_abi (gnu_v3_abi_ops);
> > + #endif
> >   }
>
> The above code is in GDB 5.1, and it isn't disabled.  I'm about to
> prepare a binary release of the DJGPP port, so I'd like to ask whether
> people here would recommend commenting defining away this code.  Is
> this only a DWARF2 issue, or is the same problem relevant to stabs,
> say?
>
No, it's relevant to STABS, too.
It's due to not properly searching virtual baseclasses.
I might still have the changes to do that somewhere, if someone wants
them.
--Dan


  reply	other threads:[~2001-11-25 16:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200110291812.f9TICtQ10130@constant.com>
2001-11-03  1:50 ` Jason Merrill
2001-11-03  7:59   ` Benjamin Kosnik
2001-11-03 10:52     ` Benjamin Kosnik
2001-11-12  8:27   ` Eli Zaretskii
2001-11-12 11:29     ` Daniel Berlin [this message]
2001-11-13 10:06       ` Benjamin Kosnik
2001-11-13 10:07         ` Daniel Berlin
2001-11-13 13:18           ` Benjamin Kosnik
2001-11-25 22:56             ` Benjamin Kosnik
2001-11-26 15:38           ` Daniel Jacobowitz
2001-11-14 20:13             ` Daniel Jacobowitz
2001-11-15  8:55             ` Daniel Berlin
2001-11-15 13:10               ` Daniel Jacobowitz
2001-11-26 17:19                 ` Daniel Jacobowitz
2001-11-26 16:53               ` Daniel Berlin
2001-11-26 16:43             ` Daniel Berlin
2001-11-15  8:48               ` Daniel Berlin
2001-11-26 16:53               ` Daniel Jacobowitz
2001-11-15  9:57                 ` Daniel Jacobowitz

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=Pine.LNX.4.33.0111251133290.24550-100000@www.cgsoftware.com \
    --to=dan@cgsoftware.com \
    --cc=bkoz@redhat.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=jason@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    /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