Subject: | |
From: | |
Reply To: | |
Date: | Fri, 28 May 1999 20:05:25 GMT |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Ernest Hill ([log in to unmask]) wrote:
: I trying run a java program on the 3000 that uses the AWT. I have set my
: display variable and have x-server and windows manager running on my pc. The
: program aborts as follows:
: SIGBUS 10* bus error
: Sig = 10; code = 18.
< stack trace snipped >
: Any ideas?
Yeah, don't use the AWT on the server :-).
Seriously, the Motif AWT is obnoxiously ill-behaved and is subject to
aborts, hangs, and unpredictable behavior. Running the GUI on the
client side and everything else on the server is a much better
configuration. We don't actually support the AWT, and I'm
seriously considering dropping it altogether in JDK 1.2.
The server side solution for AWT/JFC may improve in the future,
but I can't talk about that.
If you still want to try this, I suggest setting a global nmdebug
breakpoint at trap_handler, and getting a stack trace of the native
mode stack at the time the trap is hit. I can walk you through this
if you're unfamiliar with how it works. Send me the stack trace
and I may be able to tell you why it aborted.
: Regards,
: Ernest Hill
: eXegeSys, Inc.
: 144 S. 500 E.
: SLC, UT 84109
: (801) 799-0917
: [log in to unmask]
--
-----------------------------------------------------------------
Mike Yawn
Hewlett-Packard email [log in to unmask]
Commercial Systems Division Voice (408) 447-4367
19447 Pruneridge Ave M/S 47UA Fax (408) 447-4441
Cupertino, CA 95014
-----------------------------------------------------------------
|
|
|