SIGABORT on linux-sparc
Gary Benson
gbenson at redhat.com
Tue Apr 8 06:00:15 PDT 2008
Dennis Gilmore wrote:
> On Tuesday 08 April 2008, Sébastien Bernard wrote:
> > Gary Benson a écrit :
> > > Bernard Sébastien wrote:
> > > > 2nd: the sparc32 build goes all the way but any run led to a
> > > > SIGABORT. As show at the end.
> > > >
> > > > I'm putting the hs_err_pid1983.log in attachment produced by
> > > > the latest build of the jdk.
> > >
> > > Ah, the code that produces the hs_err_pid*.log files calls abort(),
> > > so the SIGABORT is possibly a side-effect of that.
> > >
> > >> # Internal Error (os_linux_zero.cpp:144), pid=1983, tid=1887509392
> > >> # Error: caught unhandled signal 10
> > >
> > > Is signal 10 USR1 on your machine?
> >
> > No, signal 10 is SIGBUS.
>
> Which means that memory access in not aligned
Interesting. Do you know what it was trying to access?
Cheers,
Gary
--
http://gbenson.net/
More information about the distro-pkg-dev
mailing list