public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Randolph Chung <tausq@debian.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10438: [3.3 regression] [hppa] Segfault when building jade
Date: Sat, 19 Apr 2003 15:36:00 -0000 [thread overview]
Message-ID: <20030419153601.26279.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/10438; it has been noted by GNATS.
From: Randolph Chung <tausq@debian.org>
To: Giovanni Bajo <giovannibajo@libero.it>
Cc: gcc-gnats@gcc.gnu.org, parisc-linux@lists.parisc-linux.org,
gcc-bugs@gcc.gnu.org, debian-gcc@lists.debian.org,
nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org,
Wolfgang Bangerth <bangerth@ices.utexas.edu>
Subject: Re: c++/10438: [3.3 regression] [hppa] Segfault when building jade
Date: Sat, 19 Apr 2003 08:30:56 -0700
> Confirmed. Slightly reduced testcase:
Thanks.
Running under gdb, I see:
(gdb) run bug.cxx
Starting program: /home/tausq/gcc/build-3.3/gcc/cc1plus bug.cxx
Program received signal SIGSEGV, Segmentation fault.
setup_class_bindings (name=0x401c9780, type_binding_p=1)
at ../../gcc-3.3/gcc/cp/search.c:2560
2560 if (TREE_CODE (type_binding) == TREE_LIST
(gdb) bt
#0 setup_class_bindings (name=0x401c9780, type_binding_p=1)
at ../../gcc-3.3/gcc/cp/search.c:2560
#1 0x00094410 in dfs_push_type_decls (binfo=0x401c9b40, data=0x401cf010)
at ../../gcc-3.3/gcc/cp/search.c:2615
#2 0x00092f50 in dfs_walk_real (binfo=0x401c9b40, prefn=0,
postfn=0x362c0e <__JCR_LIST__+486>, qfn=0x362bde <__JCR_LIST__+438>,
data=0x0) at ../../gcc-3.3/gcc/cp/search.c:1911
[...]
type_binding is NULL after lookup_member()...
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next reply other threads:[~2003-04-19 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 15:36 Randolph Chung [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-20 17:49 nathan
2003-04-19 15:06 Giovanni Bajo
2003-04-19 5:16 Randolph Chung
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=20030419153601.26279.qmail@sources.redhat.com \
--to=tausq@debian.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).