From: Jeremy Pack (rostovpack_at_[hidden])
Date: 2008-07-10 20:19:54
Found it. Setting ss_size to 0 causes a failure. I have set it to
MINSIGSTKSZ as described in:
This seems to fix the problem.
Here is the new code:
sigstk.ss_sp = 0;
sigstk.ss_size = MINSIGSTKSZ;
sigstk.ss_flags = SS_DISABLE;
BOOST_TEST_SYS_ASSERT( ::sigaltstack( &sigstk, 0 ) != -1 );
On Thu, Jul 10, 2008 at 5:04 PM, Gennadiy Rozental <rogeeff_at_[hidden]>
> 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.
> This is Volodia's fix for valgrind warning (see
> Can you try an alternative proposed the same thread and let me know if it
> Unsubscribe & other changes: