I am running a multi-threaded program under Debian. The application creates two threads at the time it is started. Both threads do the same work, the main thread does something different. Everything works fine, but occasionally I will get these lines in my output:
==8280== Thread 3: ==8280== Syscall param read(buf) points to unaddressable byte(s) ==8280== at 0x40ABF5B: ??? (syscall-template.S:82) ==8280== by 0x40A496D: start_thread (pthread_create.c:300) ==8280== by 0x437BA4D: clone (clone.S:130) ==8280== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==8280== This can happen hours or days after the thread was created. It is always thread 2 or 3, never thread 1. In the output, all parameters except the thread number are identical, if the error occurs. Finally, the error seems to have no effect whatsoever on the program itself, it continues running and no other errors occur. My question is, whether this is something I am doing wrong, and if so, where I could start to find out what's going on. From the stacktrace, none of the functions listed there are mine, so I'm wondering where this is actually happening. Stefan ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
