Dear Peter, I got a bug report for pfb2t1c. It is possible to crash the program under some circumstances. The submitter provided a complete testcase[1]. I've removed the attachment from this E-Mail.
Please be so kind to have a look at that. Many Thanks, Hilmar [1] http://bugs.debian.org/716508 -- http://www.hilmar-preusse.de.vu/ #206401 http://counter.li.org
--- Begin Message ---Package: pfb2t1c2pfb Version: 0.3-9 Severity: normal User: may...@forallsecure.com Usertags: mayhem pfb2t1c crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we include more information about the crash such as a core dump, the dmesg generated by the crash, and its output. Regards, The Mayhem Team (Alexandre Rebert, Thanassis Avgerinos, Sang Kil Cha, David Brumley, Manuel Egele) Cylab, Carnegie Mellon University [1] http://www.forallsecure.com/bug-reports/6ec19f5aba3c61ea0a2d7f22f04bc7dafc62be53/full_report -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.9-1-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages pfb2t1c2pfb depends on: ii libc6 2.17-6 pfb2t1c2pfb recommends no packages. pfb2t1c2pfb suggests no packages. -- no debconf information
<<< message/external-body; access-type=x-mutt-deleted; expiration="Fri, 12 Jul 2013 21:32:14 +0200"; length=125631: Unrecognized >>>
--- End Message ---
signature.asc
Description: Digital signature
