[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#219102: libc6: IBM JDK 1.3.1 core dumps



On Tue, Nov 04, 2003 at 02:59:23PM +0100, Marcus Crafter wrote:
> Hi Daniel!
> 
> Thanks for your response.
> 
> On Tue, 2003-11-04 at 14:34, Daniel Jacobowitz wrote:
> > On Tue, Nov 04, 2003 at 11:45:31AM +0100, Marcus Crafter wrote:
> > > Package: libc6
> > > Version: 2.3.2.ds1-9
> > > Severity: normal
> > > 
> > > Hi There,
> > > 
> > > Since ds1-8 the IBM JDK 1.3.1 core dumps on startup. Here's a strace of
> > > what's occuring:
> > 
> > > modify_ldt(0, 4038bf4c, 8)              = 0
> > > modify_ldt(17, {entry_number:0, base_addr:0x806dbd0, limit:16, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:0, seg_not_present:0, useable:1}, 16) = 0
> > > modify_ldt(17, {entry_number:8190, base_addr:0x806dbe8, limit:16, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:0, seg_not_present:0, useable:1}, 16) = 0
> > > sigaltstack({ss_sp=0xbfe01000, ss_flags=0, ss_size=32768}, {ss_sp=0, ss_flags=SS_DISABLE, ss_size=0}) = 0
> > > --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> > > +++ killed by SIGSEGV +++
> > > 
> > > IBM JDK 1.4.1 continues to work as normal.
> > > 
> > > If there's anything I can do to help diagnose/fix the problem please let
> > > me know.
> > 
> > Extremely unlikely, since this is a fixed bug in IBM JDK 1.3.1.
> 
> Not sure I understand you - I'm using IBM JDK 1.3.1 and are having the
> above problem - has there been a newer release of this JDK ?
> 
> Or do you mean that this is a bug that can't be fixed because it's
> present in the JDK via static linking or simliar, and not in glibc?

That's correct.  It's a problem in the JDK, and one of the changes in
later versions was to fix it.  Sorry I wasn't clear.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer



Reply to: