Re: [Valgrind-users] Valgrind newb here needs help ;-)

[Tristan V. B. <va...@to...>]

David Eriksson wrote:
> 
> (It is not advisable to start a new topic by replying to an old mail.
> Many mail agents threads messages so that this mail thread shows inside
> of the "BerkeleyDB gets bogus errno in Valgrind" thread.)

True, true. whats done is done, might as well stick to 
the bogus errno thread as opposed to starting a new thread
with `Re:...'.

I changed here:
> > #ifdef GLIBC_2_1
> > int msgsnd(int msgid,       void *msgp, size_t msgsz, int msgflg)
> > #else
> > int msgsnd(int msgid, const void *msgp, size_t msgsz, int msgflg)
> > #endif
for:
> > #ifndef GLIBC_2_1
> > int msgsnd(int msgid,       void *msgp, size_t msgsz, int msgflg)
> > #else
> > int msgsnd(int msgid, const void *msgp, size_t msgsz, int msgflg)
> > #endif

seeing as editing the config.h induced vomiting:

vg_scheduler.c: In function `do_pthread_mutex_lock':
vg_scheduler.c:2406: `PTHREAD_MUTEX_TIMED_NP' undeclared (first use in
this function)
vg_scheduler.c:2406: (Each undeclared identifier is reported only once
vg_scheduler.c:2406: for each function it appears in.)
vg_scheduler.c:2407: `PTHREAD_MUTEX_ADAPTIVE_NP' undeclared (first use
in this function)
vg_scheduler.c: In function `do_pthread_mutex_unlock':
vg_scheduler.c:2519: `PTHREAD_MUTEX_TIMED_NP' undeclared (first use in
this function)
vg_scheduler.c:2520: `PTHREAD_MUTEX_ADAPTIVE_NP' undeclared (first use
in this function)
vg_scheduler.c: In function `do_pthread_cond_wait':
vg_scheduler.c:2761: `PTHREAD_MUTEX_TIMED_NP' undeclared (first use in
this function)
vg_scheduler.c:2762: `PTHREAD_MUTEX_ADAPTIVE_NP' undeclared (first use
in this functio

Now everything compiles sweetly ;-)

Thanks for your support,
			-Tristan



-- 
Education is imposed ignorance. -- Noam Chomsky