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: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter

From: Adam Megacz <gcj at lists dot megacz dot com>
To: tromey at redhat dot com
Cc: java at gcc dot gnu dot org
Date: 29 Nov 2002 20:31:02 -0800
Subject: Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
Organization: Myself
References: <Pine.LNX.4.44.0211211859320.10438-100000@ops2.one-point.com> <001901c2924c$e75b5f10$3c16a8c0@mantatest.com> <86zns14c55.fsf@nowhere.com> <1038000382.783.14.camel@elsschot> <15842.3233.134299.96917@cuddles.cambridge.redhat.com> <86hee292ux.fsf@nowhere.com> <86adju92pv.fsf@nowhere.com> <87ptsqog3i.fsf@fleche.redhat.com> <86y97e7il2.fsf@nowhere.com> <87smxmk1xh.fsf@fleche.redhat.com> <86fztm7dbg.fsf@nowhere.com> <878yzejmp8.fsf@fleche.redhat.com>

Tom Tromey <tromey@redhat.com> writes:
> Tom> We could compile libgcj.a differently.

> Really I'd prefer not to do this.  Compiling static and dynamic
> libraries differently just makes more opportunities for obscure bugs.

I definately agree.  However, there's got to be some way to detect at
runtime if the binary is statically linked.  Any ideas?

  - a

References:
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
  - From: Jeff Sturm
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
  - From: Scott Gilbertson
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
  - From: Adam Megacz
- Re: GCJ application runs not too bad with shared libs, butcrasheswith static libs - seems to be in _Jv_MonitorEnter
  - From: Mark Wielaard
- Re: GCJ application runs not too bad with shared libs, butcrasheswith static libs - seems to be in _Jv_MonitorEnter
  - From: Andrew Haley
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
  - From: Adam Megacz
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
  - From: Adam Megacz
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
  - From: Tom Tromey
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
  - From: Adam Megacz
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
  - From: Tom Tromey
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
  - From: Adam Megacz
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
  - From: Tom Tromey

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