OK, here is the thread dump, but like I already wrote in the previous
post I only get this while running java_g so I don't know if its really
relevant.

*** panic: "../../../../src/share/javavm/runtime/classresolver.c", line
1285: assertion failure

SIGABRT   6*   abort (generated by abort(3) routine)
        stackpointer=0xbfffe370

Full thread dump Classic VM (Linux_JDK_1.2_pre-release-v2, green threads):
    "RMI ConnectionExpiration-[server.name.com:1099]" (TID:0x407d2548,
sys_thread_t:0x82a4398, state:CW) prio=5
        at java.lang.Thread.sleep(Native Method)
        at
sun.rmi.transport.tcp.TCPChannel$Reaper.run(TCPChannel.java:525)
        at java.lang.Thread.run(Thread.java:479)
    "RMI LeaseChecker" (TID:0x407d2460, sys_thread_t:0x82a0680, state:CW)
prio=5
        at java.lang.Thread.sleep(Native Method)
        at sun.rmi.transport.DGCImpl$LeaseChecker.run(DGCImpl.java:303)
        at java.lang.Thread.run(Thread.java:479)
    "RMI TCP Connection(2)-server.name.com/192.168.1.111"
(TID:0x407d0d18, sys_thread_t:0x828a780, state:CW) prio=5
        at java.net.SocketInputStream.socketRead(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:90)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:190)
        at java.io.BufferedInputStream.read1(BufferedInputStream.java:229)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:285)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:190)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:208)
        at java.io.DataInputStream.readByte(DataInputStream.java:224)
        at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:428)
        at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:607)
        at java.lang.Thread.run(Thread.java:479)
    "GC Daemon" (TID:0x407cd9e8, sys_thread_t:0x8243638, state:CW) prio=2
        at java.lang.Object.wait(Native Method)
        at sun.misc.GC$Daemon.run(GC.java:107)
    "RMI Reaper" (TID:0x407cd818, sys_thread_t:0x8234fb0, state:CW) prio=5
        at java.lang.Object.wait(Native Method)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:112)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
        at sun.rmi.transport.ObjectTable$Reaper.run(ObjectTable.java:288)
        at java.lang.Thread.run(Thread.java:479)


This continues for quite a while - atleast 2-3 pages worth of garbage.  It
happens as soon as I try to connect to the database.  This is the code
that it executes immediately before.


      Class.forName("com.sybase.jdbc.SybDriver").newInstance();
      String cInfo = "jdbc:sybase:Tds:server.name.com:20001";

      Connection dbConn = DriverManager.getConnection( cInfo, _props );

But again, this may all be unnecessary since the only thing I want to do
is have a working version of Runtime.trace*() functions.  They don't seem
to do anything normally, or I just don't know how to use them properly?

On Sat, 16 Oct 1999, Chris Abbey wrote:

> Overkill my friend... overkill. the _g versions don't change how they interact
> with the outside world, only how they work internally. Class files generated
> from javac and javac_g are the same. Unless you're debugging a failure of
> rmiregistry there is no need for rmiregistry_g. Please send the stack. The
> only thing you have to do special for working with _g is compile debuggable
> versions of *your* *native* *libs*. usually a quick `ln -s libmine.so
> libmine_g.so` is all it takes. -=Chris
> 
> 
>   cabbey at home dot net <*> http://members.home.net/cabbey
>            I want a binary interface to the brain!
> Today's opto-mechanical digital interfaces are just too slow!
> 
> 
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 


----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to