mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pedro Larroy <>
Subject Re: Catching segmentation faults in nosetests
Date Thu, 21 Jun 2018 21:14:25 GMT
A crash in the library is not an error in the test, is a different

I suggest adding these flags to get stack traces and addressing the crash
as a separate bug.

Check the return code when executing the test ($? variable in bash for
example) and it will have the value explained here (
set. Then you can mark the full suite as crashed.


On Thu, Jun 21, 2018 at 1:35 PM Marco de Abreu
<> wrote:

> Hello,
> is anybody aware of a way to catch segmentation faults as part of the
> nosetests execution and log them as ERROR? Right now, the nosetests process
> gets terminated without a stack trace or further test execution. This has
> additional significance because our result-recording that has been
> introduced in [1] does not get executed if nosetests does not run until the
> end. This means, we're not able to record and track any segmentation
> faults.
> If there is anybody in this community who has experience with catching
> segmentation faults without terminating the nosetests parent process, I'd
> really appreciate some guidance.
> Best regards,
> Marco
> [1]:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message