This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: java/1912: Segfault when handling segfault = infinite recursion
- To: nobody at gcc dot gnu dot org
- Subject: Re: java/1912: Segfault when handling segfault = infinite recursion
- From: Paul Flinders <paul at dawa dot demon dot co dot uk>
- Date: 8 Feb 2001 21:56:02 -0000
- Cc: gcc-prs at gcc dot gnu dot org,
- Reply-To: Paul Flinders <paul at dawa dot demon dot co dot uk>
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.