This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: What's up with jc1 segfaulting on mingw target? [PR 5876]

From: Adam Megacz <gcj at lists dot megacz dot com>
To: java at gcc dot gnu dot org
Date: 07 Mar 2002 16:14:30 -0800
Subject: Re: What's up with jc1 segfaulting on mingw target? [PR 5876]
Organization: Myself
References: <Pine.LNX.4.10.10203052330110.6889-100000@mars.deadcafe.org> <86eliwow18.fsf@megacz.com> <3C87FC19.1070004@waitaki.otago.ac.nz> <86it88ndnm.fsf@megacz.com> <15496.475.471716.604279@makita.cygnus.com>


Alexandre Petit-Bianco <apbianco@cygnus.com> writes:
> I started to look at it when you made the jc1 binary available, but I
> had to switch to something else and forgot. I'm going to look at it
> again, although I don't think it's the java parser's fault.

Ok, regardless, we'll probably get no sympathy from non-gcj people
since 'gcc' and 'g++' work fine -- only 'jc1' segfaults.

Thanks for helping!

  - a

-- 
"If I put copyrighted material into the 'chewy nougat center', I can
 claim the crunchy chocolate coating is an 'Access Control
 Mechanism'."                                     --lynx_user_abroad

Why Windows NT/2k/XP is unreliable: www.zappadoodle.com

References:
- What's up with jc1 segfaulting on mingw target? [PR 5876]
  - From: Adam Megacz
- Re: What's up with jc1 segfaulting on mingw target? [PR 5876]
  - From: Bryce McKinlay
- Re: What's up with jc1 segfaulting on mingw target? [PR 5876]
  - From: Adam Megacz
- Re: What's up with jc1 segfaulting on mingw target? [PR 5876]
  - From: Alexandre Petit-Bianco

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]