It could be a result of recent changes in classlib's signal handling code...
Evgueni On 11/28/06, Alexei Fedotov <[EMAIL PROTECTED]> wrote:
Alexey, I cannot find a JIRA which mentions masterSynchSignalHandler, which to my mind differentiates the stack trace. Probably it worth to file a new one. -- Thank you, Alexei On 11/27/06, Alexey Varlamov <[EMAIL PROTECTED]> wrote: > Is this a known regression? > > [junit] An unhandled error (64) has occurred. > [junit] HyGeneric_Signal_Number=00000040 > [junit] Signal_Number=00000005 > [junit] Error_Value=00000000 > [junit] Signal_Code=00000080 > [junit] Handler1=0804A7E8 > [junit] Handler2=40026667 > [junit] EDI=00000056 > [junit] ESI=00000001 > [junit] EAX=00000009 > [junit] EBX=40CD4444 > [junit] ECX=00000009 > [junit] EDX=00000005 > [junit] EIP=5651AE70 > [junit] ES=0000007B > [junit] DS=0000007B > [junit] ESP=BFFFC96C > [junit] EFlags=00000206 > [junit] CS=00000073 > [junit] SS=0000007B > [junit] EBP=BFFFCA84 > [junit] SIGABRT in VM code. > [junit] Stack trace: > [junit] 1: ?? (??:-1) > [junit] 2: abort (??:-1) > [junit] 3: masterSynchSignalHandler (??:-1) > [junit] <end of stack trace> > [junit] Test Breakpoint1.Breakpoint1 FAILED > > BUILD FAILED >
