You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Joachim Draeger <jd...@gmx.de> on 2006/12/04 20:16:58 UTC

Re: JAMES Nightly SIGSEGV Was: JAMES Server Nightly Build Report

Hi Bernd,

Cool! Didn't see that one for a long time. Is there a reward by the
ASF? ;-)
So, what says TDD to crashing VMs? ;-))

In fact StatusSessionTest involves code I changed, but that should have
been accessed in the tests before too.

Will there be anything promising in the hs_err_pid15428.log? Just
cryptic dump I guess...
Is it possible to get the output log of the test? 

I have exactly the same JVM build and clean/rerun several times.
Everything fine. The only difference is that I run 32 bit.

Well, the current JVM version is 1.5.0_10. The number of bugs fixed
since _06 is quite worrying.

I would say if there are problems with the JVM update it, not the code.
I wouldn't even know where to look.

Joachim

Am Montag, den 04.12.2006, 12:18 +0100 schrieb Bernd Fondermann:
> Wow, impressive. Probably related to current JAMES-720 works?
> 
>   Bernd
> 
> On 12/4/06, JAMES Nightly Build System <no...@devtech.com> wrote:
> >     [junit] Running org.apache.james.imapserver.handler.session.StatusSessionTest
> >     [junit] #
> >     [junit] # An unexpected error has been detected by HotSpot Virtual Machine:
> >     [junit] #
> >     [junit] #  SIGSEGV (0xb) at pc=0x00002aaaab5f84bd, pid=15428, tid=46912501790416
> >     [junit] #
> >     [junit] # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_06-b05 mixed mode)
> >     [junit] # Problematic frame:
> >     [junit] # V  [libjvm.so+0x5e44bd]
> >     [junit] #
> >     [junit] # An error report file with more information is saved as hs_err_pid15428.log
> >     [junit] #
> >     [junit] # If you would like to submit a bug report, please visit:
> >     [junit] #   http://java.sun.com/webapps/bugreport/crash.jsp
> >     [junit] #
> >
> > BUILD FAILED
> > /home/noel/ASF/james/server/trunk/build.xml:790: Test org.apache.james.imapserver.handler.session.StatusSessionTest failed
> >
> > Total time: 1 minute 49 seconds
> > --------------------------------------------------------------------
> > Done. Packages Will Be Uploaded To The Nightly Repository.
> > --------------------------------------------------------------------
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> > For additional commands, e-mail: server-dev-help@james.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Re: JAMES Nightly SIGSEGV Was: JAMES Server Nightly Build Report

Posted by Bernd Fondermann <be...@googlemail.com>.
On 12/4/06, Joachim Draeger <jd...@gmx.de> wrote:
> Hi Bernd,
>
> Cool! Didn't see that one for a long time. Is there a reward by the
> ASF? ;-)

... but only for crashing 3 times in a row at the same physical memory address.

> So, what says TDD to crashing VMs? ;-))

:-) Don't know, never done TDD. But you should really try/catch that
crash and give a better error message ;-)

> In fact StatusSessionTest involves code I changed, but that should have
> been accessed in the tests before too.

If the crash is reproducible you could put the prev version of that
file back in as a copy and try to let both be run.

> Will there be anything promising in the hs_err_pid15428.log? Just
> cryptic dump I guess...
> Is it possible to get the output log of the test?

>From Noel probably.

> I have exactly the same JVM build and clean/rerun several times.
> Everything fine. The only difference is that I run 32 bit.
>
> Well, the current JVM version is 1.5.0_10. The number of bugs fixed
> since _06 is quite worrying.
>
> I would say if there are problems with the JVM update it, not the code.
> I wouldn't even know where to look.

Yes, but we could try to narrow it down.

  Bernd

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org