Your message dated Fri, 18 Oct 2013 15:48:44 +0000
with message-id <[email protected]>
and subject line Bug#717036: fixed in crash 7.0.2-1
has caused the Debian Bug report #717036,
regarding crash: truncates filenames in error messages?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
717036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717036
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: crash
Version: 7.0.1-2
Severity: normal
Hi,
crash 7.0.1 seems to be truncating long filenames in error messages:
lindi3:~$ crash -e emacs /usr/lib/debug/boot/vmlinux-3.8-2-amd64 core
crash 7.0.1
Copyright (C) 2002-2013 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011 NEC Corporation
Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions. Enter "help copying" to see the conditions.
This program has absolutely no warranty. Enter "help warranty" for details.
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...
/usr/bin/strings: '/usr/lib/debug/boot/vmlinux-3': No such file
WARNING: kernels compiled by different gcc versions:
/usr/lib/debug/boot/vmlinux-3: (unknown)
core kernel: 4.7.2
WARNING: kernel version inconsistency between vmlinux and dumpfile
crash: incompatible arguments:
/usr/lib/debug/boot/vmlinux-3 is not SMP -- core is SMP
Usage:
crash [OPTION]... NAMELIST MEMORY-IMAGE (dumpfile form)
crash [OPTION]... [NAMELIST] (live system form)
Enter "crash -h" for details.
However, if I rename the file it is perfectly happy:
lindi3:~$ cp /usr/lib/debug/boot/vmlinux-3.8-2-amd64 vmlinux
lindi3:~$ crash -e emacs vmlinux core
crash 7.0.1
Copyright (C) 2002-2013 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011 NEC Corporation
Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions. Enter "help copying" to see the conditions.
This program has absolutely no warranty. Enter "help warranty" for details.
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...
KERNEL: vmlinux
DUMPFILE: core
CPUS: 4
DATE: Mon Jul 15 12:00:24 2013
UPTIME: 54 days, 12:58:55
LOAD AVERAGE: 0.00, 0.10, 0.37
TASKS: 185
NODENAME: lindi3
RELEASE: 3.8-2-amd64
VERSION: #1 SMP Debian 3.8.13-1
MACHINE: x86_64 (3210 Mhz)
MEMORY: 1 GB
PANIC: ""
PID: 0
COMMAND: "swapper/0"
TASK: ffffffff81614400 (1 of 4) [THREAD_INFO: ffffffff81600000]
CPU: 0
STATE: TASK_RUNNING (ACTIVE)
WARNING: panic task not found
crash>
The problem does not occur if I run crash under strace.
stap -e 'probe syscall.execve { printf("%s\n", argstr); }'
shows that crash runs
/usr/bin/strings "/usr/lib/debug/boot/vmlinux-3"
which means that the filename is truncated before it is passed to the
strings command.
The problem does not occur if I run crash under valgrind but there I
at least see the following:
==1460== Memcheck, a memory error detector
==1460== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==1460== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==1460== Command: crash -e emacs /usr/lib/debug/boot/vmlinux-3.8-2-amd64 core
==1460== Parent PID: 26631
==1460==
==1460== Conditional jump or move depends on uninitialised value(s)
==1460== at 0x4EADB3: kernel_init (kernel.c:227)
==1460== by 0x463946: main_loop (main.c:650)
==1460== by 0x74CE60: current_interp_command_loop (interps.c:326)
==1460== by 0x74E10F: captured_command_loop (main.c:258)
==1460== by 0x74BAFD: catch_errors (exceptions.c:557)
==1460== by 0x74F731: captured_main (main.c:1064)
==1460== by 0x74BAFD: catch_errors (exceptions.c:557)
==1460== by 0x74F77F: gdb_main (main.c:1079)
==1460== by 0x74F7D7: gdb_main_entry (main.c:1099)
==1460== by 0x50FB8D: gdb_main_loop (gdb_interface.c:76)
==1460== by 0x463856: main (main.c:613)
==1460==
==1460== Source and destination overlap in strcpy(0x7fefffe92, 0x7fefffe94)
==1460== at 0x4C2CA05: __GI_strcpy (mc_replace_strmem.c:439)
==1460== by 0x479DB3: pages_to_size (tools.c:5312)
==1460== by 0x4A80C4: get_memory_size (memory.c:11888)
==1460== by 0x4FC15F: display_sys_stats (kernel.c:4698)
==1460== by 0x463A64: main_loop (main.c:678)
==1460== by 0x74CE60: current_interp_command_loop (interps.c:326)
==1460== by 0x74E10F: captured_command_loop (main.c:258)
==1460== by 0x74BAFD: catch_errors (exceptions.c:557)
==1460== by 0x74F731: captured_main (main.c:1064)
==1460== by 0x74BAFD: catch_errors (exceptions.c:557)
==1460== by 0x74F77F: gdb_main (main.c:1079)
==1460== by 0x74F7D7: gdb_main_entry (main.c:1099)
==1460==
On line 227 of kernel.c gdb shows
(gdb) p p2
$1 = 0x7fffffffdf52 "8-2-amd64"
*** stack smashing detected ***: /usr/bin/crash terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7ffff6da3d17]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7ffff6da3ce0]
/usr/bin/crash(kernel_init+0x308d)[0x4ed3ea]
/usr/bin/crash(main_loop+0xdc)[0x463947]
/usr/bin/crash(current_interp_command_loop+0x1f)[0x74ce61]
/usr/bin/crash[0x74e110]
/usr/bin/crash(catch_errors+0x63)[0x74bafe]
/usr/bin/crash[0x74f732]
/usr/bin/crash(catch_errors+0x63)[0x74bafe]
/usr/bin/crash(gdb_main+0x3b)[0x74f780]
/usr/bin/crash(gdb_main_entry+0x51)[0x74f7d8]
/usr/bin/crash(gdb_main_loop+0x2c0)[0x50fb8e]
/usr/bin/crash(main+0x2c05)[0x463857]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7ffff6cc8995]
/usr/bin/crash[0x460b79]
======= Memory map: ========
00400000-00ba3000 r-xp 00000000 ca:00 708089
/usr/bin/crash
00da2000-00e61000 rw-p 007a2000 ca:00 708089
/usr/bin/crash
00e61000-02a53000 rw-p 00000000 00:00 0 [heap]
7fffeed44000-7fffefb3c000 r--p 05dce000 ca:00 847174
/usr/lib/debug/boot/vmlinux-3.8-2-amd64
7fffefb3c000-7ffff019d000 rw-p 00000000 00:00 0
7ffff02b8000-7ffff02cd000 r-xp 00000000 ca:00 827469
/lib/x86_64-linux-gnu/libgcc_s.so.1
7ffff02cd000-7ffff04cd000 ---p 00015000 ca:00 827469
/lib/x86_64-linux-gnu/libgcc_s.so.1
7ffff04cd000-7ffff04ce000 rw-p 00015000 ca:00 827469
/lib/x86_64-linux-gnu/libgcc_s.so.1
7ffff04ce000-7ffff0684000 r--p 05c19000 ca:00 847174
/usr/lib/debug/boot/vmlinux-3.8-2-amd64
7ffff0684000-7ffff0acf000 r--p 05693000 ca:00 847174
/usr/lib/debug/boot/vmlinux-3.8-2-amd64
7ffff0acf000-7ffff0cc4000 r--p 0549f000 ca:00 847174
/usr/lib/debug/boot/vmlinux-3.8-2-amd64
7ffff0cc4000-7ffff5617000 r--p 00b4d000 ca:00 847174
/usr/lib/debug/boot/vmlinux-3.8-2-amd64
7ffff5617000-7ffff6618000 rw-p 00000000 00:00 0
7ffff670b000-7ffff696a000 rw-p 00000000 00:00 0
7ffff696a000-7ffff6ca7000 r--p 00000000 ca:00 716266
/usr/lib/locale/locale-archive
7ffff6ca7000-7ffff6e49000 r-xp 00000000 ca:00 827993
/lib/x86_64-linux-gnu/libc-2.17.so
7ffff6e49000-7ffff7049000 ---p 001a2000 ca:00 827993
/lib/x86_64-linux-gnu/libc-2.17.so
7ffff7049000-7ffff704d000 r--p 001a2000 ca:00 827993
/lib/x86_64-linux-gnu/libc-2.17.so
7ffff704d000-7ffff704f000 rw-p 001a6000 ca:00 827993
/lib/x86_64-linux-gnu/libc-2.17.so
7ffff704f000-7ffff7053000 rw-p 00000000 00:00 0
7ffff7053000-7ffff7075000 r-xp 00000000 ca:00 827510
/lib/x86_64-linux-gnu/liblzma.so.5.0.0
7ffff7075000-7ffff7274000 ---p 00022000 ca:00 827510
/lib/x86_64-linux-gnu/liblzma.so.5.0.0
7ffff7274000-7ffff7275000 r--p 00021000 ca:00 827510
/lib/x86_64-linux-gnu/liblzma.so.5.0.0
7ffff7275000-7ffff7276000 rw-p 00022000 ca:00 827510
/lib/x86_64-linux-gnu/liblzma.so.5.0.0
7ffff7276000-7ffff7372000 r-xp 00000000 ca:00 828515
/lib/x86_64-linux-gnu/libm-2.17.so
7ffff7372000-7ffff7572000 ---p 000fc000 ca:00 828515
/lib/x86_64-linux-gnu/libm-2.17.so
7ffff7572000-7ffff7573000 r--p 000fc000 ca:00 828515
/lib/x86_64-linux-gnu/libm-2.17.so
7ffff7573000-7ffff7574000 rw-p 000fd000 ca:00 828515
/lib/x86_64-linux-gnu/libm-2.17.so
7ffff7574000-7ffff758b000 r-xp 00000000 ca:00 827500
/lib/x86_64-linux-gnu/libz.so.1.2.8
7ffff758b000-7ffff778a000 ---p 00017000 ca:00 827500
/lib/x86_64-linux-gnu/libz.so.1.2.8
7ffff778a000-7ffff778b000 r--p 00016000 ca:00 827500
/lib/x86_64-linux-gnu/libz.so.1.2.8
7ffff778b000-7ffff778c000 rw-p 00017000 ca:00 827500
/lib/x86_64-linux-gnu/libz.so.1.2.8
7ffff778c000-7ffff77b1000 r-xp 00000000 ca:00 828056
/lib/x86_64-linux-gnu/libtinfo.so.5.9
7ffff77b1000-7ffff79b0000 ---p 00025000 ca:00 828056
/lib/x86_64-linux-gnu/libtinfo.so.5.9
7ffff79b0000-7ffff79b4000 r--p 00024000 ca:00 828056
/lib/x86_64-linux-gnu/libtinfo.so.5.9
7ffff79b4000-7ffff79b5000 rw-p 00028000 ca:00 828056
/lib/x86_64-linux-gnu/libtinfo.so.5.9
7ffff79b5000-7ffff79d6000 r-xp 00000000 ca:00 827417
/lib/x86_64-linux-gnu/libncurses.so.5.9
7ffff79d6000-7ffff7bd5000 ---p 00021000 ca:00 827417
/lib/x86_64-linux-gnu/libncurses.so.5.9
7ffff7bd5000-7ffff7bd6000 r--p 00020000 ca:00 827417
/lib/x86_64-linux-gnu/libncurses.so.5.9
7ffff7bd6000-7ffff7bd7000 rw-p 00021000 ca:00 827417
/lib/x86_64-linux-gnu/libncurses.so.5.9
7ffff7bd7000-7ffff7bda000 r-xp 00000000 ca:00 828514
/lib/x86_64-linux-gnu/libdl-2.17.so
7ffff7bda000-7ffff7dd9000 ---p 00003000 ca:00 828514
/lib/x86_64-linux-gnu/libdl-2.17.so
7ffff7dd9000-7ffff7dda000 r--p 00002000 ca:00 828514
/lib/x86_64-linux-gnu/libdl-2.17.so
7ffff7dda000-7ffff7ddb000 rw-p 00003000 ca:00 828514
/lib/x86_64-linux-gnu/libdl-2.17.so
7ffff7ddb000-7ffff7dfc000 r-xp 00000000 ca:00 827989
/lib/x86_64-linux-gnu/ld-2.17.so
7ffff7e46000-7ffff7fe0000 r--p 06bc5000 ca:00 847174
/usr/lib/debug/boot/vmlinux-3.8-2-amd64
7ffff7fe0000-7ffff7fe5000 rw-p 00000000 00:00 0
7ffff7ff3000-7ffff7ffa000 rw-p 00000000 00:00 0
7ffff7ffa000-7ffff7ffc000 r-xp 00000000 00:00 0 [vdso]
7ffff7ffc000-7ffff7ffd000 r--p 00021000 ca:00 827989
/lib/x86_64-linux-gnu/ld-2.17.so
7ffff7ffd000-7ffff7fff000 rw-p 00022000 ca:00 827989
/lib/x86_64-linux-gnu/ld-2.17.so
7ffffffde000-7ffffffff000 rw-p 00000000 00:00 0 [stack]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0
[vsyscall]
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.8-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages crash depends on:
ii binutils 2.23.52.20130620-1
ii libc6 2.17-7
ii liblzma5 5.1.1alpha+20120614-2
ii libncurses5 5.9+20130608-1
ii libtinfo5 5.9+20130608-1
ii zlib1g 1:1.2.8.dfsg-1
crash recommends no packages.
Versions of packages crash suggests:
pn kexec-tools <none>
pn makedumpfile <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: crash
Source-Version: 7.0.2-1
We believe that the bug you reported is fixed in the latest version of
crash, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Troy Heber <[email protected]> (supplier of updated crash package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Wed, 16 Oct 2013 10:26:33 -0600
Source: crash
Binary: crash
Architecture: source amd64
Version: 7.0.2-1
Distribution: unstable
Urgency: low
Maintainer: Troy Heber <[email protected]>
Changed-By: Troy Heber <[email protected]>
Description:
crash - kernel debugging utility, allowing gdb like syntax
Closes: 717036
Changes:
crash (7.0.2-1) unstable; urgency=low
.
* Added "bison" to the BuildRequires line of the crash.spec file.
Without the patch, the build of the embedded gdb-7.6 module will
fail
unless either /usr/bin/bison or /usr/bin/yacc are available. The
failure will result in a stream of error messages from different
files that indicate:
.
multiple definition of 'main'
undefined reference to 'c_parse_escape'
undefined reference to 'ada_parse'
undefined reference to 'ada_error'
undefined reference to 'c_parse'
undefined reference to 'c_error'
undefined reference to 'cp_demangled_name_to_comp'
undefined reference to 'cp_demangled_name_parse_free'
undefined reference to 'cp_comp_to_string'
undefined reference to 'cp_new_demangle_parse_info'
.
and the build fails like so:
.
collect2: ld returned 1 exit status
make[4]: *** [gdb] Error 1
crash build failed
.
If building with rpmbuild, the new BuildRequires "bison" entry will
prevent the build from initiating unless the bison package has been
installed. If building with the tar.gz file, the build attempt will
proceed and fail unless either the bison or byacc (Berkeley Yacc)
package is installed.
.
* Fix the S390X initialization sequence on kernels that are configured
with CONFIG_STRICT_DEVMEM to automatically try /proc/kcore if:
.
(1) the /dev/crash driver is not available, and
(2) the initial /dev/mem access fails.
.
Without the patch, if /dev/mem is selected as the memory source and
it is restricted, the crash session will fail during initialization
with the error message "crash: read error: kernel virtual address:
<address> type: cpu_possible_mask".
.
* When checking whether a argument on the crash command line is a dumpfile
that may be in makedumpfile's "flattened" format, do not bother checking
character device files.
.
* Fix for the PPC64 virtual-to-physical virtual address translation
mechanism for vmalloc and user-space virtual addresses on Linux 3.10 and
later kernels. Without the patch, the message "WARNING: cannot access
vmalloc'd module memory" is displayed during initialization, and during
the crash session, if a command attempts to translate or read a vmalloc or
user-space virtual address, it will fail.
.
* Clean up all files that emit "warning: format not a string literal and no
format arguments" when compiled with -Wformat-security warning option.
All instances of fprintf, sprintf and snprintf using the format
"fprintf(fp, buf)" are replaced with "fprintf(fp, "%s", buf)". Also, the
-Wformat-security warning option has been added to the option list used
when compiling with "make warn".
.
* Fix a build failure when compiling with very old gcc-3.4.6 version on a
2.6.9-based RHEL4 IA64 host. The bfd library in gdb-7.6 is compiled with
the -Werror option, and it fails with the message "elflink.c:4733:
warning: 'idx' might be used uninitialized in this function".
.
* Fix a build failure when compiling with very old gcc-3.4.6 version on a
2.6.9-based RHEL4 S390 or S390X hosts. The embedded gdb-7.6 fails to
compile with the error message "s390-nat.c:364: error: storage size of
'iov' isn't known".
.
* Fix to properly store two-digit kernel version numbers. (closes: #717036)
.
* Fix to provide hugepage address translation for the "vtop" command on the
PPC64 architecture.
.
* Fix for the "log" command to account for the kernel data structure name
change from "log" to "printk_log" in Linux 3.11-rc4 and later kernels.
Without the patch, the message "WARNING: log buf data structure(s) have
changed" will be displayed during initialization and by the "log" command.
.
* Fix to add a linefeed after the description of the "kmem -I" option in the
"help kmem" output, which was recently added in crash-7.0.0.
.
* Document the "-s" command line option in the "crash -h|--help" output and
in the crash.8 man page to also indicate that runtime command scrolling is
turned off by default.
.
* Fix for the "irq -d" option on 2.6.25 and later X86_64 kernels to display
the Intel interrupt descriptor table contents. Without the patch, those
kernel versions would display "irq: -d option not supported or applicable
on this architecture or kernel".
.
* Fix for the "kmem -[sS]" options on Linux 3.11-rc1 and later kernels that
are configured with CONFIG_SLAB. Without the patch, the command fails
with the error message "kmem: invalid structure member offset:
.
* Fix for the "kmem <address>" and the "bt -F" options on Linux 3.8 and
later kernels that are configured with CONFIG_SLUB. Without the patch,
the command would fail with the error message "kmem: invalid structure
member offset: page_slab".
.
* Fix misspellings in the "bt" and "search" help page output.
.
* Fix for the determination of the base of the kernel's unity-mapped virtual
address region on recent ARM kernels whose "_stext" variable address has
changed from 0xc0008000 to 0xc0100000. Without the patch, the crash
session fails during invocation with the error message "crash: vmlinux and
vmcore do not match!".
.
* When printing data structures, prevent the embedded gdb from symbolically
translating pointers that are not kernel virtual addresses. Kernel or
module symbols that are not virtual addresses can be mistaken for virtual
addresses, leading to NULL pointers being invalidly translated into a
symbol name from the vmlinux or module object file. For example, in
X86_64 kernels, NULL pointers are translated into the symbol
"irq_stack_union", whose value is not a virtual address, but rather a
per-cpu offset value of 0.
.
* Fix for the "kmem -s <address>" or "kmem <address>" options on Linux 3.11
and later kernels configured with CONFIG_SLAB. Without the patch, both
commands fail with the error message "kmem: cannot resolve cache_cache".
.
* Fix to prevent the "bt" command from generating a segmentation violation
in a case where the per-cpu "current_task" variable and the runqueue's
"curr" variable did not agree, and the panic task had overflowed its
kernel stack. This led to the selection of the a starting RSP address
which belonged to the other task; without the patch, the command generated
a segmentation violation after printing the first frame of the backtrace.
Checksums-Sha1:
4599fba00824071d9e0af518e7d1ea2f6ac0c890 1115 crash_7.0.2-1.dsc
2216841453fec77f7f964f9bcd211102ad465ff0 32017268 crash_7.0.2.orig.tar.gz
2dd881e4a96f9e56e474f7e9cdd0e7d8b5625753 63834 crash_7.0.2-1.diff.gz
00498e5de0f6a5cf10de8f9fc6d776e2fad751a5 2559602 crash_7.0.2-1_amd64.deb
Checksums-Sha256:
33c31d73ce57241cf7af1c69f251754b86ad4b3c7c32fc003eb7e234d81683ac 1115
crash_7.0.2-1.dsc
203c1b0e444ae32b515febbbf113e15f56554799a2c5f2742e3a0b61baf408ca 32017268
crash_7.0.2.orig.tar.gz
8b5eeef0b44e733838dc03b46d6aeb598f4aa01bfc195a7b5bd8508ba3a6b0a7 63834
crash_7.0.2-1.diff.gz
29d38a112ef8d4f38464370b8ac8ca688a544a7a0bede64e87cffad345dd0ecf 2559602
crash_7.0.2-1_amd64.deb
Files:
e3c2ac509ae574d30b5a824bd5429898 1115 utils optional crash_7.0.2-1.dsc
b32a437eda92c25ee1c88aa846a2e044 32017268 utils optional
crash_7.0.2.orig.tar.gz
9d962482a22ab4d6bb6f3102a5d02793 63834 utils optional crash_7.0.2-1.diff.gz
17f5cc1ca4a6caf24ace047387de0ea5 2559602 utils optional crash_7.0.2-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iD8DBQFSYVCeQOr9C+GfGI4RAg+NAJ4jwmjvA5wDsYnYiztK4Zzdk3QHRQCgjwd5
reqvwum+3AHcdJvovza5zWU=
=XUjY
-----END PGP SIGNATURE-----
--- End Message ---
