On Sat, Oct 05, 2013 at 01:32:25PM -0700, Octavio Alvarez wrote:
Without -dbg, this is what I get in valgrind:
==32492== Syscall param timer_create(evp) points to uninitialised byte(s)
==32492== at 0x4E36E1A: timer_create@@GLIBC_2.3.3 (timer_create.c:83)
==32492== by 0x402607: ??? (in /usr/bin/timeout)
==32492== by 0x4022C5: ??? (in /usr/bin/timeout)
==32492== by 0x5278994: (below main) (libc-start.c:260)
==32492== Address 0x7fefffe80 is on thread 1's stack
... which is useless to the devs (or even me, if I wanted to try fixing
it out).
Looks like a noise result. Definition of timer_create is:
int timer_create(clockid_t clockid, struct sigevent *sevp, timer_t *timerid);
coreutils has:
timer_t timerid;
if (timer_create (CLOCK_REALTIME, NULL, &timerid) == 0)
...
So, yeah, timerid is unitialized--because it's just an allocated memory
location for timer_create to initialize and return a value in.
Mike Stone
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
