JProbe on 4.9

[Daren Desjardins]

I installed BSD 1.3.1 and Linux-jdk-1.3.1. The bsd jdk causes the same
hanging as 1.4.2. I was able to get the linux-jdk 1.3.1 to work a little
better than 1.4. However it causes the sig 11 included below.

If anyone has a pkg of the linux 1.4.0 or 1.4.1 port, I would be willing
to try that as well.


------
Using CATALINA_BASE:   /usr/local/jakarta-tomcat4.1
Using CATALINA_HOME:   /usr/local/jakarta-tomcat4.1
Using CATALINA_TMPDIR: /usr/local/jakarta-tomcat4.1/temp
Using JAVA_HOME:       /usr/local/linux-sun-jdk1.3.1
JProbe Warning: jvminfo.xml file has been modified and may not be
officially sup
ported.
JProbe(tm) Profiler Version 5.0.1
(c)1998-2003 by Quest Software Inc.
All rights reserved. JProbe is a trademark of Quest Software Inc.
SIGSEGV   11*  segmentation violation
    si_signo [11]: SIGSEGV   11*  segmentation violation
    si_errno [0]: Success
    si_code [12]: unknown siginfo
        stackpointer=0x2dfbaff4

Full thread dump Classic VM (1.3.1_10-b03, green threads):
    "Signal dispatcher" (TID:0x29a213b8, sys_thread_t:0x81ae9b0,
state:R) prio=5
    "main" (TID:0x29a211b0, sys_thread_t:0x804d998, state:R) prio=5
Monitor Cache Dump:
Registered Monitor Dump:
    utf8 hash table: <unowned>
    JNI pinning lock: <unowned>
    JNI global reference lock: <unowned>
    BinClass lock: <unowned>
    Class linking lock: <unowned>
    System class loader lock: <unowned>
    Code rewrite lock: <unowned>
    Heap lock: <unowned>
    _JProbe Pool Lock_: <unowned>
    _JProbe Socket Read Lock_: <unowned>
    _JProbe VMState Lock_: <unowned>
    _JProbe Socket Lock_: <unowned>
    _JProbe Lock_: <unowned>
    _JProbe Suspend Monitor_: <unowned>
    _JProbe Client Data Lock_: <unowned>
    _JProbe Log Lock_: <unowned>
    Monitor cache lock: owner "Signal dispatcher" (0x81ae9b0) 1 entry
    Dynamic loading lock: <unowned>
    Monitor IO lock: <unowned>
    User signal monitor: <unowned>
    Child death monitor: <unowned>
    I/O monitor: <unowned>
    Alarm monitor: <unowned>
        Waiting to be notified:
            <unknown thread> (0x808af70)
    Thread queue lock: owner "Signal dispatcher" (0x81ae9b0) 1 entry
    Monitor registry: owner "Signal dispatcher" (0x81ae9b0) 1 entry

Press any key to continue . . .

On Wed, 2004-02-25 at 11:36, Daren Desjardins wrote:
> 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.
> 
> _______________________________________________
> freebsd-java at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-java
> To unsubscribe, send any mail to "freebsd-java-unsubscribe at freebsd.org"