public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Paul Flinders <paul@dawa.demon.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: java/1912: Segfault when handling segfault = infinite recursion
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <20010208215602.32706.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR java/1912; it has been noted by GNATS.
From: Paul Flinders <paul@dawa.demon.co.uk>
To: tromey@redhat.com
Cc: paul@dawa.demon.co.uk, gcc-gnats@gcc.gnu.org
Subject: Re: java/1912: Segfault when handling segfault = infinite recursion
Date: Thu, 8 Feb 2001 21:58:23 +0000 (GMT)
Tom Tromey writes:
> >>>>> "Paul" == paul <paul@dawa.demon.co.uk> writes:
>
> Paul> #2 0x4018966a in _Jv_type_matcher (info=0x83dcde8, match_info=0xffffffff,
> Paul> exception_table=0x8392d64) at ../../../gcc/libjava/exception.cc:62
>
> I'm wondering if this is the same exception handling problem someone
> reported a few days ago.
>
> Andrew?
It definately looks similar.
I was able to do a little more debugging than Jeff - I think that the
problem is that some of the exception table entries have match_info
fields which are 0xffffffff. I haven't traced it back farther than
that as I don't actually understand the code which produces
__EXCEPTION_TABLE__, not the relationship of that to the table that
find_exception_handler is scanning.
>From rodrigc@mediaone.net Sun Apr 01 00:00:00 2001
From: Craig Rodrigues <rodrigc@mediaone.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/1709
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010224211600.30802.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg01701.html
Content-length: 507
The following reply was made to PR c++/1709; it has been noted by GNATS.
From: Craig Rodrigues <rodrigc@mediaone.net>
To: rodrigc@mediaone.net, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: c++/1709
Date: Sat, 24 Feb 2001 16:05:54 -0500
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1709&database=gcc
Please close this.
I just tested with:
gcc version 3.0 20010223 (prerelease)
and it now works.
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@mediaone.net
next reply other threads:[~2001-04-01 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-01 0:00 Paul Flinders [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-12 23:46 Tom Tromey
2003-01-11 23:16 Nathanael Nerode
2001-04-01 0:00 Andrew Haley
2001-04-01 0:00 paul
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=20010208215602.32706.qmail@sourceware.cygnus.com \
--to=paul@dawa.demon.co.uk \
--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).