From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Klaas Gadeyne <Klaas.Gadeyne@mech.kuleuven.ac.be>,
gdb@sources.redhat.com
Subject: Re: gdb namespaces/wrapper bug?
Date: Thu, 15 Jan 2004 15:43:00 -0000 [thread overview]
Message-ID: <16390.46294.814398.906197@localhost.redhat.com> (raw)
In-Reply-To: <20040115144949.GA26765@nevyn.them.org>
Daniel Jacobowitz writes:
>
> 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).
I actually was just looking at a similar bug against RH gdb, which I just
verified with current CVS:
Do
b main
run
p foo
with this, and you get the infinite loop + segfault:
struct derived;
struct base
{
static derived bar;
};
struct derived : base
{
};
derived base::bar;
base foo;
int main()
{
return 0;
}
the problem seems to be cp_print_static_field. If you set print
static-member off of course it all works. (gcc 3.2.2)
elena
next prev parent reply other threads:[~2004-01-15 15:43 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
2004-01-15 15:43 ` Elena Zannoni [this message]
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=16390.46294.814398.906197@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=Klaas.Gadeyne@mech.kuleuven.ac.be \
--cc=drow@mvista.com \
--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