This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Line numbers in stack traces [was: GCJ application runs not too bad with shared libs, but crasheswith] static libs - seems to be in _Jv_MonitorEnter
In an ideal world, where we all have infinite time...
Andrew Haley <aph@redhat.com> writes:
> * works without debugging info,
Right, this would be the deciding factor: debug info is used if
available; otherwise, use reflection data
> * doesn't require additional processes to be created,
> * removes a dependency on external tools that may not be present and
> occasionally don't do what we want.
This just means that we have to reimplement addr2line or convince the
FSF to LGPL it so it can be included in libgcj.
> the right thing to do is to make thr choice configurable or
> have some time of runtime auto-detection.
I had that working at one point (runtime auto-detection); it's not too
hard.
- a
- References:
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, butcrasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, butcrasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, but crasheswith static libs - seems to be in _Jv_MonitorEnter
- Re: GCJ application runs not too bad with shared libs, but crasheswithstatic libs - seems to be in _Jv_MonitorEnter
- Line numbers in stack traces [was: GCJ application runs not too bad with shared libs, but crasheswith]static libs - seems to be in _Jv_MonitorEnter