On Feb 26, 2011, at 1:21 AM, Jeff Johnson wrote: > > On Feb 26, 2011, at 1:12 AM, Mark Hatle wrote: > >> I tried to revert the rpmdb/legacy.c back to 5.3, 5.2. and 5.1 versions. >> They >> all have the same issue. >> >> I attempted the same within the prelink side of things, and as far as I can >> tell >> the code for writing to stdout for RPM validation hasn't changed in about 5 >> years. >> > > And rpmdb/legacy.c hasn't changed meaningfully (afaik) in 5+ years either. > >> So I'm at a bit of a loss to explain whats wrong, and why it suddenly >> happened. :( >> > > Then its time to vary something else. > > Is the problem all platform or specific to this platform? > > Does the problem exist with rpm-5.3.x (also "RPM ACID") > or rpm-5.1.9 (which will need dbconvert.sh run)? >
This is the only bracketing of the problem reported: > Ok, I've done more digging. If I run this within gdb, I'm suddenly seeing an > error message appear on the screen: > prelink: Couldn't write file to standard output: Broken pipe > S.?..... <filename> > However, if I use gdb and step through the fork/exec in rpmdb/legacy.c at > around > like 128.. I don't get the error message -- and it comes back with a "." for > a > valid md5um. (If I run this without GDB, I get the '?' and no error message > from prelink.) Heisenbug's that disappear with gdb single stepping are timing/racy usually. Salt in some nanosleep's and see what happens. My guess is that the child is running before the parent, so add a sleep(5) after the fork before the exec. 73 de Jeff
smime.p7s
Description: S/MIME cryptographic signature
