I am getting the following error when building any Boost tests on OS X 10.5: ====== BEGIN OUTPUT ====== Test setup error: system_error produced by: ::sigaltstack( &sigstk, 0 ) != -1: Cannot allocate memory EXIT STATUS: 200 ====== END OUTPUT ====== Anyone seen this before? Jeremy Pack
On 10 Jul 2008, at 20:42, Jeremy Pack wrote:
I am getting the following error when building any Boost tests on OS X 10.5:
====== BEGIN OUTPUT ====== Test setup error: system_error produced by: ::sigaltstack( &sigstk, 0 ) != -1: Cannot allocate memory
EXIT STATUS: 200 ====== END OUTPUT ======
Anyone seen this before?
I have the same problems Matthias
ditto. On Jul 10, 2008, at 3:35 PM, Matthias Troyer wrote:
On 10 Jul 2008, at 20:42, Jeremy Pack wrote:
I am getting the following error when building any Boost tests on OS X 10.5:
====== BEGIN OUTPUT ====== Test setup error: system_error produced by: ::sigaltstack ( &sigstk, 0 ) != -1: Cannot allocate memory
EXIT STATUS: 200 ====== END OUTPUT ======
Anyone seen this before?
I have the same problems
Matthias
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/ listinfo.cgi/boost
Jeremy Pack <rostovpack <at> gmail.com> writes:
I am getting the following error when building any Boost tests on OS X 10.5:
====== BEGIN OUTPUT ====== Test setup error: system_error produced by: ::sigaltstack( &sigstk, 0 ) != -1: Cannot allocate memory
EXIT STATUS: 200 ====== END OUTPUT ======
Anyone seen this before?
Nope. Did u try to google for what might be the cause? R u using latest trunk? Gennadiy
On Thu, Jul 10, 2008 at 1:19 PM, Gennadiy Rozental <rogeeff@gmail.com> wrote:
<snip>
Nope.
Did u try to google for what might be the cause?
Yep. No luck.
R u using latest trunk?
Always :) I was hoping someone would know what was going on. I guess I'll just have to do a binary search to figure out which revision is the last one that works... I'll post here if I can find it. Jeremy
Gennadiy, The revision causing the fault is probably 46159. 46158 does not have the issues.
From the looks of the CL, the revised version is more correct - but I'm guessing it opens up some error that was hidden before.
http://svn.boost.org/trac/boost/changeset/46159/trunk/boost/test/impl/execution_monitor.ipp?old=45763&old_path=trunk%2Fboost%2Ftest%2Fimpl%2Fexecution_monitor.ipp Jeremy On Thu, Jul 10, 2008 at 3:01 PM, Jeremy Pack <rostovpack@gmail.com> wrote:
On Thu, Jul 10, 2008 at 1:19 PM, Gennadiy Rozental <rogeeff@gmail.com> wrote:
<snip>
Nope.
Did u try to google for what might be the cause?
Yep. No luck.
R u using latest trunk?
Always :)
I was hoping someone would know what was going on. I guess I'll just have to do a binary search to figure out which revision is the last one that works...
I'll post here if I can find it.
Jeremy
Jeremy Pack <rostovpack <at> gmail.com> writes:
Gennadiy,
The revision causing the fault is probably 46159. 46158 does not have the issues.
From the looks of the CL, the revised version is more correct - but I'm guessing it opens up some error that was hidden before.
Weird. This is Volodia's fix for valgrind warning (see http://lists.boost.org/boost-users/2008/06/37312.php) Can you try an alternative proposed the same thread and let me know if it works? Gennadiy
Gennadiy, Found it. Setting ss_size to 0 causes a failure. I have set it to MINSIGSTKSZ as described in: http://www.gnu.org/software/libtool/manual/libc/Signal-Stack.html This seems to fix the problem. Here is the new code: #ifdef BOOST_TEST_USE_ALT_STACK stack_t sigstk; sigstk.ss_sp = 0; sigstk.ss_size = MINSIGSTKSZ; sigstk.ss_flags = SS_DISABLE; BOOST_TEST_SYS_ASSERT( ::sigaltstack( &sigstk, 0 ) != -1 ); #endif Jeremy On Thu, Jul 10, 2008 at 5:04 PM, Gennadiy Rozental <rogeeff@gmail.com> wrote:
Jeremy Pack <rostovpack <at> gmail.com> writes:
Gennadiy,
The revision causing the fault is probably 46159. 46158 does not have the issues.
From the looks of the CL, the revised version is more correct - but I'm guessing it opens up some error that was hidden before.
Weird.
This is Volodia's fix for valgrind warning (see http://lists.boost.org/boost-users/2008/06/37312.php)
Can you try an alternative proposed the same thread and let me know if it works?
Gennadiy
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
participants (4)
-
Gennadiy Rozental -
Jeremy Pack -
Matthias Troyer -
Ronald Garcia