A customer faces with abnormal end during compilation.

CONFIGURATION :
  OS : Solaris 9
  VM : HotSpot Server VM 1.3.1_06


INVESTIGATION :
   
STACK TRACE:
......
#8 <signal handler called>
#9 0x001d0854 in %%%
jp/co/fit/vfreport/PDF#PoutputT(Ljp/co/fit/vfreport/TextDataAccess;Ljp/co/fit/vfreport/TextPitch;Ljava/lang/StringBuffer;III)Z
(0x17ce75f0, 0x0, 0xffffff60, 0x1cf0d4, 0x14, 0x139fd550)
#10 0x001cba50 in %%%
jp/co/fit/vfreport/PDF#drawPrimitiveText(Ljp/co/fit/vfreport/TextDataAccess;Ljava/lang/StringBuffer;II)V
(0x139fd874, 0x17ce75f0, 0x17ce75f0, 0x1d75b0, 0x1c, 0x139fd768)
......

--- stack trace end ---

COMMENT by CUSTOMER :
 According to the trace, PoutputT method terminates abnormally because of
stack inconsistency of JAVA allication while interpreter runs.

PoutputT method has been already compiled (please see below) .
The status is "java_method alive=(not_entrant )".
So, PoutputT method has created "uncommon trap".

----

NMethod(609)::virtual jp.co.fit.vfreport.PDF::PoutputT
Compiled {method}{0xf80f35b0} 'PoutputT'
'(Ljp/co/fit/vfreport/TextDataAccess;Ljp/co/fit/vfreport/TextPitch;Ljava/lang/StringBuffer;III)Z' in
'jp/co/fit/vfreport/PDF'
((nmethod*)0xfba3c6d0) for method 0xf80f35b0 {java_method alive=(not_entrant )}:
main code [0xfba3d150,0xfba41d4c] = 19452
exception code [0xfba41d4c,0xfba41d58] = 12
stub code [0xfba41d58,0xfba42238] = 1248
relocation [0xfba3c77c,0xfba3d150] = 2516
oops [0xfba49be4,0xfba4a078] = 1172
scopes data [0xfba42238,0xfba49390] = 29016
scopes pcs [0xfba49390,0xfba49738] = 936
handler table [0xfba49738,0xfba49b90] = 1112
nul chk table [0xfba49b90,0xfba49be4] = 84

-----
###@###.### 2005-1-27 23:36:08 GMT