This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: SimpleDateFormat thread problems?
- From: Tom Tromey <tromey at redhat dot com>
- To: Vladimir Leven <vladimirl at wrx-ca dot com>
- Cc: Bryce McKinlay <mckinlay at redhat dot com>, java at gcc dot gnu dot org
- Date: 10 May 2004 12:16:14 -0600
- Subject: Re: SimpleDateFormat thread problems?
- References: <40633001.3090605@wrx-ca.com> <409FA422.4070103@wrx-ca.com><409FC17C.3030701@redhat.com> <409FC71E.4020600@wrx-ca.com>
- Reply-to: tromey at redhat dot com
>>>>> "Vladimir" == Vladimir Leven <vladimirl@wrx-ca.com> writes:
Vladimir> (which is updated by another thread, but presumably
Vladimir> this.time = System.currentTimeMillis is atomic?)
Assignment of a `long' is not guaranteed to be atomic. This comes
from the JLS or perhaps the JVM spec, I forget.
Vladimir> Related question: Is there a way to dump the stack trace for a given
Vladimir> thread? I can only seem to look at the stack trace for the currently
Vladimir> running thread.
In gdb, just switch to the thread you're interested in with the
"thread" command, then "bt".
Outside of gdb, no, I don't think there is a way.
Tom