Java 1.1.8 sigserv 11
Shannon -jj Behrens
jj at nttmcl.com
Wed Apr 9 13:20:02 PDT 2003
Aren't signal 11's usually the result of bad memory (e.g. bad memory)?
On Wed, Apr 09, 2003 at 03:12:24PM +0100, Ernst de Haan wrote:
> Wasn't this due to some kernel option or so? I don't remember the exact
> details though. Search the archives.
> On Wednesday 09 April 2003 15:49, FT wrote:
> > Hello,
> > I've installed compat3x-i386-4.4.20020925 and JDK 1.1.8 from ports on
> > FreeBSD 4.7 stable.
> > And now I have problem: when I try to execute, for example, javac, I
> > get following message:
> > SIGSEGV 11* segmentation violation
> > Full thread dump:
> > Monitor Cache Dump:
> > Registered Monitor Dump:
> > Monitor IO lock: <unowned>
> > Child death monitor: <unowned>
> > Event monitor: <unowned>
> > I/O monitor: <unowned>
> > Alarm monitor: <unowned>
> > Memory allocation lock: <unowned>
> > Monitor registry: <unowned>
> > Thread Alarm Q:
> > Abort trap
> > I know that I'm not first who confront with this problem, but I can't
> > find how to solve it.
Hacker is to software engineer as
Climbing Mt. Everest is to building a Denny's there.
More information about the freebsd-java