[apport] foremost crashed with SIGSEGV in strlen()

Bug #86952 reported by xtsbdu3reyrbrmroezob
14
Affects Status Importance Assigned to Milestone
foremost (Ubuntu)
Invalid
Medium
MOTU

Bug Description

Binary package hint: foremost

$ foremost -v -i PE2900-010200.hdr -o /tmp/bios

Ran that on a file that was a BIOS image on an amd64 Feisty laptop. Check backtrace maybe? I can give it if needed...
--
Kristian Hermansen

ProblemType: Crash
Date: Thu Feb 22 02:16:17 2007
Dependencies:
 tzdata 2007b-0ubuntu1
 belocs-locales-bin 2.4-2ubuntu1
 locales 2.3.23
 libc6 2.5-0ubuntu11
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/foremost
Package: foremost 1.3-1
ProcCmdline: foremost -v -i PE2900-010200.hdr -o /tmp/bios
ProcCwd: /tmp
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: foremost
StacktraceTop:
 strlen () from /lib/libc.so.6
 vfprintf () from /lib/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Uname: Linux khermans-laptop 2.6.20-8-generic #2 SMP Tue Feb 13 01:14:41 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report.

Changed in foremost:
assignee: nobody → motu
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:strlen () from /lib/libc.so.6
vfprintf () from /lib/libc.so.6
audit_msg ()
write_audit_header ()
open_audit_file ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Lenin (gagarin) wrote :

Meanwhile there's newer versions of foremost, can you still reproduce this?

Revision history for this message
xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob) wrote : Re: [Bug 86952] Re: [apport] foremost crashed with SIGSEGV in strlen()

On Nov 25, 2007 4:51 AM, Gürkan Sengün <email address hidden> wrote:
> Meanwhile there's newer versions of foremost, can you still reproduce
> this?

I no longer have AMD64 laptop available for testing, so I will mark
this bug as INVALID, and if anyone rediscovers it in a future version,
they can reopen this report...
--
Kristian Erik Hermansen

Changed in foremost:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.