tags 506239 moreinfo unreproducible
kthxbye

On Wed, Nov 19, 2008 at 05:13:25PM +0000, Mike Crowe wrote:
> Valgrind still returns with an exit code of zero when the following
> program is run despite being called as "valgrind --error-exitcode=42".
> 
> The valgrind output also continues even after the shell prompt
> returns.
> 
> I've reproduced this on etch using valgrind-3.2.1-1 and a backported
> valgrind-3.3.1-2 from lenny. Occasionally valgrind behaves correctly
> but most of the time it does not.
> 
> If I compile the original release valgrind-3.3.1 tarball myself then
> it does not show either symptom.
> 
> I have no reason to believe that this problem is boost-specific. It
> was just the easiest way for me to produce a minimal test case.
> 
> 
>  #include <boost/thread.hpp>
>  
>  void CrashThread()
>  {
>      int *foo = reinterpret_cast<int *>(3);
>      *foo = 42;
>  }
>  
>  int main()
>  {
>      boost::thread thread(CrashThread);
>      thread.join();
>      return 0;
>  }

I cannot reproduce this with the valgrind version in unstable. Does this still
happen to you?

Cheers

-- 
perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'

Attachment: signature.asc
Description: Digital signature

Reply via email to