Re: [Valgrind-users] BerkeleyDB gets bogus errno in Valgrind

[Nicholas N. <nj...@ca...>]

On Mon, 12 May 2003, Julian Seward wrote:

> Er, yes.  There's definitely some still wrong with errno handling
> on both my glibc-2.3.2 systems.  The attached test program I made
> doesn't work properly -- the perror calls print different stuff when
> running on V.  I'll look into it more tomorrow night.  The strange
> thing is the numbers returned by the errno uses are right, it's just
> that when perror reads errno it gets junk.
>
> Nick, can you lmk if it works on R H 7.1?  Thx,

Hmm, I don't think so:

[~/grind/head] a.out
f1 = 0x804b8a8, errno1 = 4
wurble1: Interrupted system call
f2 = (nil), errno2 = 2
wurble2: No such file or directory
f3 = (nil), errno3 = 2
wurble3: No such file or directory

[~/grind/head] vg6 a.out
==557== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux.
==557== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward.
==557== Using valgrind-cvs-head-2003-04-23, a program supervision framework for x86-linux.
==557== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward.
==557== Estimated CPU clock rate is 1405 MHz
==557== For more details, rerun with: -v
==557==
f1 = 0x40fd8194, errno1 = 0
wurble1: Success
f2 = (nil), errno2 = 2
wurble2: No such file or directory
f3 = (nil), errno3 = 2
wurble3: No such file or directory
==557==
==557== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6 from 2)
==557== malloc/free: in use at exit: 564 bytes in 2 blocks.
==557== malloc/free: 9 allocs, 7 frees, 2408 bytes allocated.
==557== For a detailed leak analysis,  rerun with: --leak-check=yes
==557== For counts of detected errors, rerun with: -v