Name: rlT66838			Date: 07/30/97


1. Even the silliest standalone program (that uses the AWT) compiled 
   with JDK 1.1.2 or 1.1.3 barfs when it is displayed on an NCD X 
   terminal (but 1.0.2 works great, which is a bit odd).

2. Here is an example (F.java):

import java.awt.Frame ;
import java.awt.Button ;

public class F extends Frame {

  public static void main(String[] args) {
    new F() ;
  }

  F() {
    add("Center", new Button("HAR!")) ;
    resize(200,200) ;
    show() ;
  }
}

3. Here is what happens when this is run:

SIGSEGV   11*  segmentation violation
    si_signo [11]: SIGSEGV   11*  segmentation violation
    si_errno [0]: Error 0
    si_code [1]: SEGV_ACCERR [addr: 0x14]

	stackbase=EFFFE810, stackpointer=EFFFD3F0

Full thread dump:
    "AWT-Motif" (TID:0xed304ab8, sys_thread_t:0xee7d0de0, state:MW) prio=5
	java.lang.Thread.run(Thread.java)
    "AWT-Input" (TID:0xed304a98, sys_thread_t:0xee800de0, state:CW) prio=5
    "AWT-EventQueue-0" (TID:0xed304a80, sys_thread_t:0xee830de0, state:CW) prio=5
	java.lang.Object.wait(Object.java)
	java.awt.EventQueue.getNextEvent(EventQueue.java:118)
	java.awt.EventDispatchThread.run(EventDispatchThread.java:55)
    "Finalizer thread" (TID:0xed300220, sys_thread_t:0xeeb20de0, state:CW) prio=1
    "Async Garbage Collector" (TID:0xed3001d8, sys_thread_t:0xeeb50de0, state:CW) prio=1
    "Idle thread" (TID:0xed300190, sys_thread_t:0xeeb80de0, state:R) prio=0
    "Clock" (TID:0xed3000d0, sys_thread_t:0xeebb0de0, state:CW) prio=12
    "main" (TID:0xed3000a8, sys_thread_t:0x40fb0, state:R) prio=5 *current thread*
	sun.awt.motif.MFramePeer.<init>(MFramePeer.java:59)
	sun.awt.motif.MToolkit.createFrame(MToolkit.java:120)
	java.awt.Frame.addNotify(Frame.java:139)
	java.awt.Window.show(Window.java:130)
	F.<init>(F.java:13)
	F.main(F.java:7)
Monitor Cache Dump:
    java.awt.EventQueue@ED304A30/ED351C90: <unowned>
	Waiting to be notified:
	    "AWT-EventQueue-0"
    <unknown key> (0xeeb50de0): <unowned>
	Waiting to be notified:
	    "Async Garbage Collector"
    sun.awt.motif.MToolkit@ED304A00/ED351BA0: owner "main" (0x40fb0, 1 entry)
	Waiting to enter:
	    "AWT-Motif"
	Waiting to be notified:
	    "AWT-Input"
Registered Monitor Dump:
    Thread queue lock: <unowned>
    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>
	Waiting to be notified:
	    "Finalizer thread"
    Monitor IO lock: <unowned>
    Child death monitor: <unowned>
    Event monitor: <unowned>
    I/O monitor: <unowned>
    Alarm monitor: <unowned>
	Waiting to be notified:
	    "Clock"
    Sbrk lock: <unowned>
    Monitor cache expansion lock: <unowned>
    Monitor registry: owner "main" (0x40fb0, 1 entry)
Thread Alarm Q:
    sys_thread_t 0xeeb50de0   [Timeout in 440 ms]

Pretty, isn't it?

4. N/A

5. It seems not to like something in Motif.  And yet, we are
   using CDE 1.0.1 as shipped with Solaris.


cak

company - INRS-Telecommunications , email - ###@###.###
======================================================================