Bug#716622: [Mayhem] Bug report on pcmanx-gtk2: pcmanx crashes with exit status 139

Skip to first unread message

Alexandre Rebert

Jul 10, 2013, 3:39:58 PM7/10/13
to Debian Bug Tracking System:
Package: pcmanx-gtk2
Version: 1.1-2
Severity: normal
User: may...@forallsecure.com
Usertags: mayhem

pcmanx 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.

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/08b25223fb5f0c3c3445d7bae4085be812dab5e5/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 pcmanx-gtk2 depends on:
ii libc6 2.17-6
ii libfontconfig1 2.9.0-7.1
ii libgdk-pixbuf2.0-0 2.28.2-1
ii libglib2.0-0 2.36.3-2
ii libgtk2.0-0 2.24.18-1
ii libltdl7 2.4.2-1.2
ii libnotify4 0.7.5-2
ii libpango1.0-0 1.32.5-5+b1
ii libstdc++6 4.8.1-4
ii libx11-6 2:1.6.0-1
ii libxft2 2.3.1-1

pcmanx-gtk2 recommends no packages.

pcmanx-gtk2 suggests no packages.

-- no debconf information

Debian Bug Tracking System

Sep 26, 2023, 12:32:30 PM9/26/23
to Debian FTP Masters
Your message dated Tue, 26 Sep 2023 16:20:08 +0000
with message-id <E1qlAnA-...@fasolo.debian.org>
and subject line Bug#1044138: Removed package(s) from unstable
has caused the Debian Bug report #716622,
regarding [Mayhem] Bug report on pcmanx-gtk2: pcmanx crashes with exit status 139
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 ow...@bugs.debian.org

716622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Reply all
Reply to author
0 new messages