From: Troels W. H. <tr...@th...> - 2003-07-14 08:37:49
|
Summary: it works. My original testsystem is using glibc 2.3.2-4.80.6 which contains a workaround for the problem. Fortunately I had another RH8 box around with stock glibc (2.2.93-5) installed. $ cat /etc/redhat-release Red Hat Linux release 8.0 (Psyche) $ uname -a Linux testus 2.4.18-26.8.0 #1 Mon Feb 24 10:21:42 EST 2003 i686 i686 i386 GNU/Linux $ rpm -q glibc glibc-2.2.93-5 $ valgrind --version valgrind-1.9.6 --> both testcases succeed $ rpm -q glibc glibc-2.3.2-4.80 --> both testcases fail $ valgrind --version valgrind-cvs-head-2003-07-13 --> both testcases succeed Troels > -----Original Message----- > From: val...@li... > [mailto:val...@li...] On Behalf > Of Julian Seward > Sent: 13. juli 2003 03:29 > To: Troels Walsted Hansen > Cc: val...@li... > Subject: Re: [Valgrind-users] BerkeleyDB gets bogus errno in Valgrind > > > > I think I have fixed this problem. Can you build from cvs and see > if the situation has improved? |