|
From: Anders T. <to...@lu...> - 2004-03-31 13:57:19
|
I always get this error at startup when I have a threaded application. ==15592== Syscall param sigaction(act) contains uninitialised or unaddressable byte(s) ==15592== at 0x3C091EB5: __libc_sigaction (in /lib/tls/libc-2.3.2.so) ==15592== by 0xFFF: ??? ==15592== Address 0x4FFFE700 is on thread 1's stack Is it a "real" error, or is it something to do with Valgrind? I'm using valgrind-2.1.1, gcc 3.3.3 and libc 2.3.2 /Anders Torger |
|
From: Nicholas N. <nj...@ca...> - 2004-04-02 14:11:11
|
On Wed, 31 Mar 2004, Anders Torger wrote: > I always get this error at startup when I have a threaded application. > > ==15592== Syscall param sigaction(act) contains uninitialised or > unaddressable byte(s) > ==15592== at 0x3C091EB5: __libc_sigaction (in /lib/tls/libc-2.3.2.so) > ==15592== by 0xFFF: ??? > ==15592== Address 0x4FFFE700 is on thread 1's stack > > Is it a "real" error, or is it something to do with Valgrind? > > I'm using valgrind-2.1.1, gcc 3.3.3 and libc 2.3.2 I'm not aware of any way it could be a Valgrind artifact. The stack trace looks bogus, though... Sorry, not much help. N |