Re: [sage-devel] OS X (or BSD) testers needed

2018-02-23 Thread Dima Pasechnik
On Friday, February 23, 2018 at 4:18:54 PM UTC, Justin C. Walker wrote: > > > > On Feb 23, 2018, at 02:40 , Dima Pasechnik > wrote: > > > > And without a possibility to write a full dump on the same OSX machine > > > > $ ulimit -c 1 > > $ ./forksigaltstack > > status = 4 > > > > So your

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-23 Thread Justin C. Walker
> On Feb 23, 2018, at 08:19 , Justin C. Walker wrote: > > >> On Feb 23, 2018, at 00:19 , 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? > > The system produces it, conditionally (I think). > > I

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-23 Thread Justin C. Walker
> On Feb 23, 2018, at 00:19 , 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? The system produces it, conditionally (I think). If it does, it will either be in ~/Library/Logs/{DiagnosticReports, CrashRe

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-23 Thread Justin C. Walker
> On Feb 23, 2018, at 02:40 , Dima Pasechnik wrote: > > 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… See man 2 wait :-

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-23 Thread Dima Pasechnik
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 Fr

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-23 Thread Dima Pasechnik
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

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-23 Thread Jeroen Demeyer
Thanks everybody! It seems that OS X always gives the "wrong" result. -- 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 p

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-23 Thread Jeroen Demeyer
On 2018-02-22 21:19, Justin C. Walker wrote: the crash log. What is that? How do you produce such a log? -- 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-de

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-22 Thread Justin C. Walker
> On Feb 22, 2018, at 07:10 , Jeroen Demeyer wrote: > > If you have an OS X (or BSD) system installed with development tools, please > run: > > uname -a > gcc forksigaltstack.c -o forksigaltstack && ./forksigaltstack > > and post the output. This code is a reduction of a test failure in cysig

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-22 Thread John H Palmieri
$ uname -a Darwin John-iMac-2017.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 $ gcc forksigaltstack.c -o forksigaltstack && ./forksigaltstack status = 4 On Thursday, February 22, 2018 at 7:24:00 AM UTC-8, David Roe wrote: >

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-22 Thread David Roe
Darwin Davids-MBP 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64 status = 4 On Thu, Feb 22, 2018 at 4:21 PM, David Joyner wrote: > On Thu, Feb 22, 2018 at 10:16 AM, Jeroen Demeyer > wrote: > > On 2018-02-22 16:13, David Joyner wrot

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-22 Thread David Joyner
On Thu, Feb 22, 2018 at 10:16 AM, Jeroen Demeyer wrote: > On 2018-02-22 16:13, David Joyner wrote: >> >> clang: error: no such file or directory: 'forksigaltstack.c' >> clang: error: no input files > > > Sorry, I obviously forgot to mention the step "copy the attached file > forksigaltstack.c to t

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-22 Thread Jeroen Demeyer
On 2018-02-22 16:13, David Joyner wrote: clang: error: no such file or directory: 'forksigaltstack.c' clang: error: no input files Sorry, I obviously forgot to mention the step "copy the attached file forksigaltstack.c to the current working directory" and then run uname -a gcc forksigaltsta

Re: [sage-devel] OS X (or BSD) testers needed

2018-02-22 Thread David Joyner
On Thu, Feb 22, 2018 at 10:10 AM, Jeroen Demeyer wrote: > If you have an OS X (or BSD) system installed with development tools, please > run: > > uname -a > gcc forksigaltstack.c -o forksigaltstack && ./forksigaltstack > > and post the output. This code is a reduction of a test failure in jeeves

[sage-devel] OS X (or BSD) testers needed

2018-02-22 Thread Jeroen Demeyer
If you have an OS X (or BSD) system installed with development tools, please run: uname -a gcc forksigaltstack.c -o forksigaltstack && ./forksigaltstack and post the output. This code is a reduction of a test failure in cysignals. I consider that failure to be an OS X bug. I want to have some