From: Troels W. H. <tr...@th...> - 2003-05-07 09:02:46
|
Sorry, I managed to forget to attach the script. Here's the script, as well as two straces, created with the below commands, on a RH8+glibc 2.3.3 machine. strace python dbboguserrno.py 2> strace-normal.txt strace valgrind python dbboguserrno.py 2> strace-valgrind.txt Both traces show the below syscall, but the instance running in Valgrind seems to get EAGAIN instead... open("nosuchfile.db", O_RDONLY|O_NONBLOCK|O_LARGEFILE) = -1 ENOENT (No such file or directory) Troels > -----Original Message----- > From: Nicholas Nethercote [mailto:nj...@he...] On > Behalf Of Nicholas Nethercote > Sent: 7. mai 2003 10:43 > To: Troels Walsted Hansen > Cc: val...@li... > Subject: Re: [Valgrind-users] BerkeleyDB gets bogus errno in Valgrind > > > On Wed, 7 May 2003, Troels Walsted Hansen wrote: > > > This is the expected behavior of the program. > > > > rpmdb._rpmdb.DBNoSuchFileError: (2, 'No such file or directory') > > > > This is what happens in Valgrind. RH8 and RH9 uses > BerkeleyDB 4.0.14, > > > rpmdb._rpmdb.DBAgainError: (11, 'Resource temporarily unavailable -- > > nosuchfile.db: Resource temporarily unavailable') > > It's possible that Valgrind's doing something slightly > different with file > handling that means you get a different behaviour. Do you have more > information about what exactly is happening to prompt this > error? Eg. is > it trying to open a file with the open() system call, or > something like > that? It's very difficult to know what the problem is from your > description so far. > > N > |