Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Feb 2004 11:36:39 -0500
From:      Daren Desjardins <desjardins@canada.com>
To:        Greg Lewis <glewis@eyesbeyond.com>
Cc:        java@FreeBSD.org
Subject:   Re: JProbe on 4.9
Message-ID:  <1077726999.1199.8.camel@lithium.stabilia.com>
In-Reply-To: <20040225162239.GA34599@misty.eyesbeyond.com>
References:  <1077653842.7043.3.camel@lithium.stabilia.com> <200402250936.58783.ernst.dehaan@nl.wanadoo.com> <1077721890.1199.3.camel@lithium.stabilia.com> <20040225162239.GA34599@misty.eyesbeyond.com>

next in thread | previous in thread | raw e-mail | index | archive | help
That would be super handy. Right now im trying to build JDK 1.3 to see
how that works.

I tried using the ctrl-\ but nothing happens. Ill see about getting it
to run under gdb. Its a pain because its a collection of scripts setting
things up prior to invoking java.

On Wed, 2004-02-25 at 11:22, Greg Lewis wrote:
> On Wed, Feb 25, 2004 at 10:11:30AM -0500, Daren Desjardins wrote:
> > Ahh, I did not realize linux jdk defaults to the linux/usr directory
> > when  browsing. Explains a lot :)
> > 
> > As for the hanging, I have not been able to find anything yet. There is
> > no messages or errors printed, it simply displays the splash screen and
> > nothing more. I know JPRobe has a lot of issues with jdk 1.4.2 which may
> > be causing the hangs. I have 1.4.2 bsd jdk and linux jdk installed. I
> > will have to do some digging to see if I can get a jdk 1.4.0 or 1.4.1
> > going.
> 
> We had a port of jdk 1.4.1 you could go back to if you wanted to.
> 
> You could get a stack trace of where its hanging (in the java sense)
> by hitting Ctrl-\.  You could run it under gdb and get a C stack trace
> too.  That might help you figure out what it is, although it sounds like
> they simply have trouble with 1.4.2.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1077726999.1199.8.camel>