FULL PRODUCT VERSION :
bertha:~$ java -version
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)

ADDITIONAL OS VERSION INFORMATION :
Linux bertha 2.6.12-1-686-smp #1 SMP Tue Sep 27 13:10:31 JST 2005 i686 GNU/Linux

A DESCRIPTION OF THE PROBLEM :
it's not possible to launch Java applications with ltrace(1), presumably because of the messing about with LD_LIBRARY_PATH the JVM does during its long long trek to starting up.

if instead you have a running JVM, attaching ltrace(1) to it via pid causes the JVM to hang.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. java -jar SwingSet2.jar
2. jps | grep SwingSet2
3. ltrace -p <pid>

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
a trace of the library calls Java's making.
ACTUAL -
the JVM is now hung.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
$ ltrace -p 22425
--- SIGSTOP (Stopped (signal)) ---
--- SIGSTOP (Stopped (signal)) ---
--- SIGSTOP (Stopped (signal)) ---
--- SIGSTOP (Stopped (signal)) ---
--- SIGSTOP (Stopped (signal)) ---
--- SIGSTOP (Stopped (signal)) ---
--- SIGSTOP (Stopped (signal)) ---
--- SIGSTOP (Stopped (signal)) ---

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
don't run ltrace(1).