🚀 go-pugleaf

Andrew Bennett wrote:

> Definitely not a JBCL problem.

Okay, I've removed the jcbl newsgroup from the Newsgroups list, then.
:-)

> I perceive it to be a JDK problem. Does this work in 1.1.5?

In 1.1.5, the entire java executable crashes with an access violation
exception when I exit the program.

I have discovered that if with 1.1.2 I do a ctrl-break instead of ctrl-c
when
the program hangs, the VM dumps information about what it was doing
when I pulled the plug. It says:

----------------------------------------------------------------------
Full thread dump:
    "Screen Updater" (TID:0xf7a388, sys_thread_t:0x8b4d90, Win32ID:0xc3,
state:S) prio=4
        java.lang.Object.wait(Object.java:315)
        sun.awt.ScreenUpdater.nextEntry(ScreenUpdater.java:78)
        sun.awt.ScreenUpdater.run(ScreenUpdater.java:98)
    "AWT-Windows" (TID:0xf74cc0, sys_thread_t:0x8af6c0, Win32ID:0xa1,
state:R) prio=5
        sun.awt.windows.WToolkit.run(WToolkit.java:108)
        java.lang.Thread.run(Thread.java:474)
    "AWT-EventQueue-0" (TID:0xf74be8, sys_thread_t:0x8af810,
Win32ID:0xd2, state:R) prio=5
        sun.awt.windows.WComponentPeer.finalize(WComponentPeer.java:255)
        java.lang.Runtime.exit(Runtime.java:85)
        java.lang.System.exit(System.java:488)
       
KetenSim.ResourceMover.RMFrame.fileExit_actionPerformed(RMFrame.java:126)
       
KetenSim.ResourceMover.RMFrame_menuFileExit_ActionAdapter.actionPerformed(RMFrame.java:180)
        java.awt.MenuItem.processActionEvent(MenuItem.java:336)
        java.awt.MenuItem.processEvent(MenuItem.java:307)
        java.awt.MenuComponent.dispatchEventImpl(MenuComponent.java:146)
        java.awt.MenuComponent.dispatchEvent(MenuComponent.java:138)
        java.awt.EventDispatchThread.run(EventDispatchThread.java:65)
    "Finalizer thread" (TID:0xf700d0, sys_thread_t:0x897a70,
Win32ID:0xd1, state:CW) prio=2
    "main" (TID:0xf700a8, sys_thread_t:0x8992c0, Win32ID:0xda, state:S)
prio=5
Monitor Cache Dump:
    sun.awt.ScreenUpdater@F7A388/FDA1D8: <unowned>
        Waiters: 1
    sun.awt.windows.WPanelPeer@F7A530/FDAE88: owner "AWT-EventQueue-0"
(0x8af810, 1 entry)
Registered Monitor Dump:
    Thread queue lock: <unowned>
        Waiters: 1
    Name and type hash table lock: <unowned>
    String intern lock: <unowned>
    JNI pinning lock: <unowned>
    JNI global reference lock: <unowned>
    BinClass lock: <unowned>
    Class loading lock: <unowned>
    Java stack lock: <unowned>
    Code rewrite lock: <unowned>
    Heap lock: <unowned>
    Has finalization queue lock: <unowned>
    Finalize me queue lock: <unowned>
        Waiters: 1
    Monitor cache expansion lock: <unowned>
    Monitor registry: <unowned>
---------------------------------------------------------------------------

This does not mean much to me, but I think I do understand now that this
is
a JDK problem, and not a Borland problem...

-- 
Leo Breebaart  <leo@lspace.org>