From: Bart V. A. <bva...@ac...> - 2010-09-07 16:48:41
|
On Tue, Sep 7, 2010 at 1:10 PM, Christian Borntraeger <bor...@de...> wrote: > > Am 07.09.2010 13:04, schrieb Bart Van Assche: > > The above commit indeed removes r11304. Revision 11304 was committed > > too early - it was committed while I was searching for the cause of an > > assertion failure triggered by a signal handler that was invoked on an > > alternate stack. > > > > None of the callers of the modified function should invoke it with len == 0. > > > Look at coregrind/m_main.c:2188 > > VG_TRACK( die_mem_stack, > seg->start, > the_iifii.initial_client_SP - VG_STACK_REDZONE_SZB > - seg->start ); > > If the environment happens to be the right size, > (the_iifii.initial_client_SP - VG_STACK_REDZONE_SZB) might be exactly > on a page start and therefore identical to seg-start. This would > result in len=0, no? > > (coincidentally seen here on my system). Thanks for the feedback. Does r11342 (or later) work on your system without triggering an assertion failure ? Bart. |