"Patrick J. McNerthney" wrote:
>
> I was just trying to figure how to do this in Linux, I am use to the
> CTRL-BREAK combo in NT.
>
> I just tried this on my Linux machine and it didn't work. Any obvious
> things to check ???
It runs straight out of the box for me (RedHat 6.1, Blackdown jdk1.2
> I don't know if you know this or not but hitting [CTRL][\] (control
backslash)
> will cause your application to dump a full stack trace of all your
threads.
> Very handy for debugging.
I was just trying to figure how to do this in Linux, I am use to the
CTRL-BREAK combo in NT.
I just tried thi
[EMAIL PROTECTED] wrote:
>
> Pardon me for one more question - how to check thread status from command
> line (like "ps" is used to check process status from command line) on Linux?
> I'm new in Linux.
I don't know if you know this or not but hitting [CTRL][\] (control backslash)
will cause your
an
>
> Regards,
>
>
> Lee
>
> -Original Message-
> From: Nathan Meyers [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 19, 1999 4:36 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Thread in the Linux's JVM
ssage-
From: Nathan Meyers [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 19, 1999 4:36 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Thread in the Linux's JVM
On Fri, Nov 19, 1999 at 03:54:42PM -0600, [EMAIL PROTECTED] wrote:
>
> [Nathan]
> The J
The JNI/C code DOES execute in the same thread as the Java thread that
invokes it. You must consider this in your design. Also, you can't
have a "non-Java" thread perform a call-back to a Java object.
Brett Smith
Subject:
Re: Thread in the Linux's JVM
Date:
Jacob Nikom wrote:
>
> So, you think that JNI does not represent any specific issues in
> Java multithreading? Does the JNI/C code executes in the same thread
> as the Java method which invoked it?
JNI code is just the native "back end" of certain Java methods. It runs
in whatever thread the cal
So, you think that JNI does not represent any specific issues in
Java multithreading? Does the JNI/C code executes in the same thread
as the Java method which invoked it?
Also, what about event-dispatching thread? In the documentation about
InvokeLater() method there is no any mention that you h
:[EMAIL PROTECTED]]
> Sent: Monday, November 08, 1999 10:14 PM
> To: [EMAIL PROTECTED]
> Cc: Evandro Luquini; [EMAIL PROTECTED]
> Subject: Re: Thread in the Linux's JVM
>
> Jacob Nikom wrote:
>
> > It would be nice to know more about multithreading features of Linux
&
Jacob Nikom wrote:
> It would be nice to know more about multithreading features of Linux
> JVM.
There are two threading models. If you run with green threads, there is
no preemption, and control passes between threads either with yield()
calls or possibly with other calls that can block (such a
Jacob Nikom wrote:
> I use SwingWorker class. If I don't have JNI methods I don't have
> to use yield() method. If I replace my Java methods with JNI calls
> I must use yield(), otherwise the application simply does not work.
> There is no mentioning of yield() method in any SwingWorker-related
>
Hi,
Thank you for bringing up this question. I also have problems with
multiple threads in Linux. In my case the behavior of threads with
JNI is different from pure Java behavior.
I use SwingWorker class. If I don't have JNI methods I don't have
to use yield() method. If I replace my Java method
Title: Thread in the Linux's JVM
Hi,
In the JavaWord article called "programming Java threads in the real world, Part 1( http://www.javaworld.com/jw-09-1998/jw-09-threads.html)", the author sad that "Java's promise of platform independence falls flat on its face in t
Title: Thread in the Linux's JVM
Hi,
In the JavaWord article called "programming Java threads in the real world, Part 1( http://www.javaworld.com/jw-09-1998/jw-09-threads.html)", the author sad that "Java's promise of platform independence falls flat on its face in t
On Fri, Nov 19, 1999 at 03:54:42PM -0600, [EMAIL PROTECTED] wrote:
>
> [Nathan]
> The JVM is a multi-threaded native application. Most of the time it's
> running native code that implements an interpreter, but some of the time
> it's running native code that doesn't happen to be in the interprete
-Original Message-
From: Nathan Meyers [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 18, 1999 3:32 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Thread in the Linux's JVM
On Thu, Nov 18, 1999 at 11:59:04AM -0600, [EMAIL PROTECTED] wrote:
> This sounds to me l
On Thu, Nov 18, 1999 at 11:59:04AM -0600, [EMAIL PROTECTED] wrote:
> This sounds to me like Java and C/C++ native code can talk to each other
> only if they (java and native code) are in the same thread. Is it right, or
> in the same process?
What do you mean "talk to each other"?
The JVM is a
At 11:59 11 Nov 1999 -0600, [EMAIL PROTECTED] wrote:
> This sounds to me like Java and C/C++ native code can talk to each other
> only if they (java and native code) are in the same thread. Is it right, or
> in the same process?
>
> Suppose C/C++ native code creates another thread within the sh
; [EMAIL PROTECTED]
Subject: Re: Thread in the Linux's JVM
Jacob Nikom wrote:
>
> So, you think that JNI does not represent any specific issues in
> Java multithreading? Does the JNI/C code executes in the same thread
> as the Java method which invoked it?
JNI code is just the nat
19 matches
Mail list logo
