[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#699205: linux-image-3.7-trunk-amd64: ps, pgrep and pkill segfault after upgrade from 3.7.1-1~experimental.2 to 3.7.3-1~experimental.1



Jonathan Nieder <jrnieder@gmail.com> writes:

>> after updating the linux-image-3.7-trunk-amd64 from
>> 3.7.1-1~experimental.2 to 3.7.3-1~experimental.1 today and rebooting,
>> the tools ps, pgrep and pkill (package procps) are always segfaulting:
>
> Just to check: if you downgrade to 3.7.1 again, do the segfaults go
> away?  (Historical versions of Debian packages are available from
> http://snapshot.debian.org)

Confirmed.


>> I'll try to provide a backtrace at the end of the week if noone else
>> can reproduce this in the meantime; debugging this issue is a pain as
>> it requires reboots, especially since the procps test suite runs (and
>> fails) despite 'nocheck' in DEB_BUILD_OPTIONS.
>
> Sounds like http://bugs.debian.org/656508

I'm afraid not. #656508 is also about the test suite failing, but the
output is quite different. With 3.7.3-1~experimental.1 it caught the
segfaults (good in general), but even with 3.7.1-1~experimental.2 it
fails the "lib" tests because of a missing file:

=== Begin ===
                === lib tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./lib.test/fileutils.exp ...
ERROR: tcl error sourcing ./lib.test/fileutils.exp.
ERROR: couldn't execute "/home/sascha.silbe/src/deb/procps-3.3.3/testsuite/lib.test/fileutils_badfd.sh": no such file or directory
    while executing
"spawn $badfd"
    (file "./lib.test/fileutils.exp" line 13)
    invoked from within
"source ./lib.test/fileutils.exp"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source ./lib.test/fileutils.exp"
    invoked from within
"catch "uplevel #0 source $test_file_name""
Running ./lib.test/strutils.exp ...
=== End ===


Have just filed a separate bug about that.


>>                                                 A pre-built -dbg
>> package would have been nice.
>
> Sounds worth a separate report. :)

I've mentioned it in the FTBFS report. Maybe a gentle nudge is
enough. :)


>>                               I wonder what got of the Squeeze release
>> goal "Automatic creation of debug packages for the entire archive"...
>
> I know that for my library package (liblzma) I haven't bothered but
> would be happy to take care of it if I knew there were a push for this
> systemwide.  Might be worth starting a discussion on debian-policy@.

Maybe one of these days I'll do (probably on debian-devel first,
though). I seem to have a knack of triggering crashes, especially in
applications using lots of libraries that don't ship a -dbg package.

Sascha

Attachment: pgpSXgVGG0qct.pgp
Description: PGP signature


Reply to: