And without a possibility to write a full dump on the same OSX machine

$ ulimit -c 1

$ ./forksigaltstack

status = 4


So your status= is affected by availability of core dump facility in some 
way.

Oy gevalt...




On Friday, February 23, 2018 at 10:19:16 AM UTC, Dima Pasechnik wrote:
>
> On Friday, February 23, 2018 at 8:20:05 AM UTC, Jeroen Demeyer wrote:
>>
>> On 2018-02-22 21:19, Justin C. Walker wrote: 
>> > the crash log. 
>>
>> What is that? How do you produce such a log? 
>>
>> appears to me as an output of some logging tool (not sure which one)
>
> Do you have access to an OSX system? You can use lldb, you know...
>
> $ ulimit -c unlimited
>
> $ cc -g forksigaltstack.c -o forksigaltstack 
>
> $ ./forksigaltstack
>
> status = 132 
>
> $ ls -l /cores/core*  # see which one was the last
> $ lldb -c /cores/core.663 
>
> (and you'll see that you get a stack overflow at line 18 of your code...)
>
> By the way, it's status 132 here, not 4
>
> $ uname -a
>
> Darwin Dimas-MacBook-Air.local 17.4.0 Darwin Kernel Version 17.4.0: Sun 
> Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64 x86_64
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to