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: printing exceptions?

From: Richard Henderson <rth at redhat dot com>
To: Alexandre Oliva <aoliva at redhat dot com>
Cc: tromey at redhat dot com, Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>, Java Discuss List <java at gcc dot gnu dot org>
Date: Tue, 5 Mar 2002 19:25:58 -0800
Subject: Re: printing exceptions?
References: <873czimtqw.fsf@creche.redhat.com> <3C81649B.7000809@waitaki.otago.ac.nz> <87k7sqr62x.fsf@creche.redhat.com> <orsn7elk8l.fsf@free.redhat.lsd.ic.unicamp.br> <871yeyo675.fsf@creche.redhat.com> <oradtml7hm.fsf@free.redhat.lsd.ic.unicamp.br>

On Wed, Mar 06, 2002 at 12:07:01AM -0300, Alexandre Oliva wrote:
> I don't understand why what you're seeing is the exact converse,
> namely, that by omitting -shared-libgcc, you get correct a working
> program&shared library, but by leaving it in, things break.
> Richard, any suggestions?

None but to actually debug it.


r~

References:
- printing exceptions?
  - From: Tom Tromey
- Re: printing exceptions?
  - From: Bryce McKinlay
- Re: printing exceptions?
  - From: Tom Tromey
- Re: printing exceptions?
  - From: Alexandre Oliva
- Re: printing exceptions?
  - From: Tom Tromey
- Re: printing exceptions?
  - From: Alexandre Oliva

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