hao huang wrote:
>
> I crossed over some informaiton on the internet last week says that only
> green threads is working on JDK 1.2 or earlier realese (may fixed in 1.3, I
> did not try). You can search on Sun's web site bug report for details. Good
> luck!
>
> Hao Huang
> Avienda Technologies
> Tel: 404-262-4358
> Email: [EMAIL PROTECTED]
>
> -----Original Message-----
> From: Francois Boisvert [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 23, 2000 1:38 PM
> To: Java-Linux
> Subject: SIGSEGV 11* segmentation violation
>
> Hi!
>
> I have a package that I want to run under Linux (Red Hat 6.2) and when the
> program calls a native function through JNI I get:
>
> SIGSEGV 11* segmentation violation
> si_signo [11]: SIGSEGV 11* segmentation violation
> si_errno [0]: Success
> si_code [0]: SI_USER [pid: 0, uid: 0]
> stackpointer=0xbfffed34
>
> Full thread dump Classic VM (Linux_JDK_1.2.2_RC4, native threads):
> "AWT-Motif" (TID:0x40e7c0a0, sys_thread_t:0x8274860, state:R, native
> ID:0x1807) prio=5
>
> Does anybody has an idea on how to fix that!
The JNI tutorials I've seen all seem to neglect showing you how to
link JNI stuff with the correct thread model. I haven't learned the
details yet, but you may have to specify a thread library when you
link your shared library. You may also have to specify a thread
package to use when you launch your JVM.
See pages 97 and 141 of Sheng Liang's "The Java Native Interface
Programmer's Guide and Specification." This is the only place I've
seen thread model conflicts discussed.
--
Joi Ellis Software Engineer
Aravox Technologies [EMAIL PROTECTED], [EMAIL PROTECTED]
No matter what we think of Linux versus FreeBSD, etc., the one thing I
really like about Linux is that it has Microsoft worried. Anything
that kicks a monopoly in the pants has got to be good for something.
- Chris Johnson
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
