Re: [Valgrind-developers] error with fork+pthreads

[Tom H. <th...@cy...>]

In message <418...@ey...>
          Eyal Lebedinsky <ey...@ey...> wrote:

> I keep up-to-date with cvs. I have this error reported for a long
> time now (over a year?), but decided it is time to report it.
> 
> The small attached script demonstrates the error. I get this output,
> note the "Invalid read of size 1" errors. The parent printf is good,
> the child provokes an error.
> 
> $ sh ~/zz32.sh
> gcc (GCC) 3.3.4 (Debian 1:3.3.4-13)
> Copyright (C) 2003 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> /home/eyal/zz32.c(78) will pthread_attr_init
> /home/eyal/zz32.c(81) pthread_attr_init=0
> forking, name='/home/eyal/zz32'
> forked, name='/home/eyal/zz32', pid=10148
> ==10148== Thread 2:
> ==10148== Invalid read of size 1
> ==10148==    at 0x1B9BF6A9: _IO_vfprintf (in /lib/tls/libc-2.3.2.so)
> ==10148==    by 0x1B9C11EB: (within /lib/tls/libc-2.3.2.so)
> ==10148==  Address 0x52BFED94 is not stack'd, malloc'd or (recently) free'd
> ==10148==
> ==10148== Thread 2:
> ==10148== Invalid read of size 1
> ==10148==    at 0x1B9E6A20: _IO_default_xsputn (in /lib/tls/libc-2.3.2.so)
> ==10148==  Address 0x52BFED94 is not stack'd, malloc'd or (recently) free'd
> forked, name='/home/eyal/zz32', pid=0

I think this is just another case of the environment problem
you reported on the bug tracker - some data from the parent is
not being considered as accessible in the child for some reason.

Tom

-- 
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/