From: Daniel Jacobowitz <drow@mvista.com>
To: Klaas Gadeyne <Klaas.Gadeyne@mech.kuleuven.ac.be>
Cc: gdb@sources.redhat.com
Subject: Re: gdb namespaces/wrapper bug?
Date: Thu, 15 Jan 2004 14:49:00 -0000 [thread overview]
Message-ID: <20040115144949.GA26765@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0401151319510.20336@f012>
On Thu, Jan 15, 2004 at 01:37:45PM +0100, Klaas Gadeyne wrote:
> namespace BASE
> {
> class Foo
> namespace WRAPPED
> {
> class Foo : public BASE::Foo
> This compiles and runs just fine (compile wrapper_object.cpp, compile
> wrapper.cpp linking with wrapper_object.o), but when debugging the code
> with gdb (I only tried with both 5.3-debian and 6.0-debian (the latest
> from testing and unstable)) and trying to display the mywrapped variable,
> gdb enters in a infinite loop:
>
> (gdb) display mywrapped
> 1: mywrapped = {<Foo> = {<Foo> = ....
>
> and finally segfaults.
Could you try CVS gdb? I think the segfault has been fixed. I may be
mistaken about that, though. This is related to
lookup_transparent_type, which David has been doing some work on (and
has more pending).
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-15 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 12:37 Klaas Gadeyne
2004-01-15 14:49 ` Daniel Jacobowitz [this message]
2004-01-15 15:43 ` Elena Zannoni
2004-01-15 16:30 ` Klaas Gadeyne
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=20040115144949.GA26765@nevyn.them.org \
--to=drow@mvista.com \
--cc=Klaas.Gadeyne@mech.kuleuven.ac.be \
--cc=gdb@sources.redhat.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