Control: tags -1 + patch ❦ 18 janvier 2015 01:49 +0100, Lucas Nussbaum <lu...@lucas-nussbaum.net> :
> During a rebuild of all packages in jessie (in a jessie chroot, not a > sid chroot), your package failed to build on amd64. I am able to reproduce this bug as well. The failure happens in pmap test on an unreachable process (PID 1). pmap just exits with status 1 in this case because it isn't able to open /proc/1/smaps. The test is expecting to see the process PID and name as the first line. I can't see why the test would have worked at some point. Either you are root and you will get the full map or you are not and you won't get the expected first line because it is only displayed if a user is able to open /proc/1/smaps. Here is a patch just removing the test.
Description: don't test pmap against unreachable process When running as root, the test will fail because 1 will be reachable. When running as non-root, the test will fail because pmap doesn't even try to read the process map when /proc/XX/smaps is not readable. Bug-Debian: https://bugs.debian.org/775624 Last-Update: 2015-01-23 Index: procps-3.3.9/testsuite/pmap.test/pmap.exp =================================================================== --- procps-3.3.9.orig/testsuite/pmap.test/pmap.exp +++ procps-3.3.9/testsuite/pmap.test/pmap.exp @@ -57,12 +57,3 @@ expect_table $test $pmap_generic_header set test "pmap double extra extended output" spawn $pmap -XX $mypid expect_table $test $pmap_generic_header "\[^=\]+" "\[= \]+" - -set test "pmap X with unreachable process" -spawn $pmap -X 1 -expect_pass $test "$pmap_initname\$" - -set test "pmap XX with unreachable process" -spawn $pmap -XX 1 -expect_pass $test "$pmap_initname\$" -
-- Make sure input cannot violate the limits of the program. - The Elements of Programming Style (Kernighan & Plauger)
signature.asc
Description: PGP signature