[zeromq-dev] make check failed
Brian Knox
briank at talksum.com
Wed May 30 02:10:54 CEST 2012
Ah, duh! Thanks, that makes perfect sense.
Here's the latest...
[Thread 0x7fffbe7fc700 (LWP 21596) exited]
[Thread 0x7fffbdffb700 (LWP 21597) exited]
[New Thread 0x7fffbd7fa700 (LWP 21598)]
[Thread 0x7fffbd7fa700 (LWP 21598) exited]
[New Thread 0x7fffbcff9700 (LWP 21599)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff5bc6700 (LWP 21534)]
0x00007ffff797a818 in main_arena () from /lib/libc.so.6
Brian
On Tue, May 29, 2012 at 7:13 PM, Lourens Naudé <lourens at methodmissing.com>wrote:
> Hi Brian,
>
> strace doesn't help much here as it traces system calls between the user
> process and the Kernel. The segfault's in user space and thus a stack trace
> is more helpful in tracking it down ( although system calls leading up to
> the segfault may help as well ). Note that tests are wrapper scripts and
> needs to be invoked with (g)libtool execute mode to run with gdb. On OS X :
>
> glibtool --mode=execute gdb test_shutdown_stress
>
> In your environment most likely :
>
> libtool --mode=execute gdb test_shutdown_stress
>
> This is what I got ( exhausted file descriptors, normal on Darwin ) :
> https://gist.github.com/2831352
>
> - Lourens
>
>
> On Tue, May 29, 2012 at 11:46 PM, Brian Knox <briank at talksum.com> wrote:
>
>> Definitely still segfaulting (sorry, got swamped with work!)
>>
>> Did a rebuild, 1/17 tests failed, and manually run segfaults:
>>
>> $ ./test_shutdown_stress
>> test_shutdown_stress running...
>> [1] 11992 segmentation fault ./test_shutdown_stress
>>
>> I've attached the output of strace -f ./test_shutdown_stress - not at the
>> end it appears to exit with 0 again - but maybe the fuller trace will be
>> helpful to something.
>>
>> Let me know if there's anything else I can do as far as gathering
>> information!
>>
>> Brian
>>
>>
>> On Tue, May 29, 2012 at 2:52 PM, Brian Knox <briank at talksum.com> wrote:
>>
>>> gah!
>>>
>>> that implies it's failing except when I strace it....
>>>
>>> give me a bit.
>>>
>>>
>>> On Tue, May 29, 2012 at 1:42 PM, Pieter Hintjens <ph at imatix.com> wrote:
>>>
>>>> On Tue, May 29, 2012 at 12:26 PM, Brian Knox <briank at talksum.com>
>>>> wrote:
>>>>
>>>> > Pieter - just a heads up that I've verified a failing test on zmq
>>>> head, on
>>>> > arch linux:
>>>> > I've attached a strace.
>>>>
>>>> Not sure how to read the trace, it looks fine and ends with exit (0).
>>>>
>>>> Doesn't fail on my 64-bit Ubuntu 11.10... :/
>>>>
>>>> Could you post a normal stack trace?
>>>>
>>>> -Pieter
>>>> _______________________________________________
>>>> zeromq-dev mailing list
>>>> zeromq-dev at lists.zeromq.org
>>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>>>
>>>
>>>
>>
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>
>>
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120529/5051ae22/attachment.htm>
More information about the zeromq-dev
mailing list