[apport] gunzip crashed with SIGSEGV in read()

Bug #89040 reported by Martin Pitt
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gzip (Ubuntu)
Invalid
Undecided
Martin Pitt

Bug Description

Binary package hint: gzip

This is a test bug. Please ignore.

ProblemType: Crash
Architecture: amd64
Date: Thu Mar 1 21:49:36 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /bin/gunzip
Package: gzip 1.3.9-2
ProcCmdline: gunzip -f
ProcCwd: /home/martin/ubuntu/chroots
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/martin/bin:/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
Signal: 11
SourcePackage: gzip
StacktraceTop:
 read () from /lib/libc.so.6
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux donald 2.6.20-9-generic #2 SMP Sun Feb 25 22:59:06 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport
Revision history for this message
Martin Pitt (pitti) wrote :

Closing, as this is just a dummy bug to test apport-retrace.

Changed in gzip:
assignee: nobody → pitti
status: Unconfirmed → Rejected
Revision history for this message
Martin Pitt (pitti) wrote : Test subject

Test comment

Revision history for this message
Martin Pitt (pitti) wrote : Test attachment subject

Test attachment comment

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

StacktraceTop:__read_nocancel () from /lib/libc.so.6
read_buffer (fd=0, buf=0x631dc0, cnt=32768) at util.c:157
fill_inbuf (eof_ok=1) at util.c:125
get_method (in=0) at gzip.c:1244
treat_stdin () at gzip.c:646

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__read_nocancel () from /lib/libc.so.6
read_buffer (fd=0, buf=0x631dc0, cnt=32768) at util.c:157
fill_inbuf (eof_ok=1) at util.c:125
get_method (in=0) at gzip.c:1244
treat_stdin () at gzip.c:646

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

StacktraceTop:__read_nocancel () from /lib/libc.so.6
read_buffer (fd=0, buf=0x631dc0, cnt=32768) at util.c:157
fill_inbuf (eof_ok=1) at util.c:125
get_method (in=0) at gzip.c:1244
treat_stdin () at gzip.c:646

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

StacktraceTop:__read_nocancel () from /lib/libc.so.6
read_buffer (fd=0, buf=0x631dc0, cnt=32768)
fill_inbuf (eof_ok=1) at util.c:125
get_method (in=0) at gzip.c:1244
treat_stdin () at gzip.c:646

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

StacktraceTop:__read_nocancel () from /lib/libc.so.6
read_buffer (fd=0, buf=0x631dc0, cnt=32768) at util.c:157
fill_inbuf (eof_ok=1) at util.c:125
get_method (in=0) at gzip.c:1244
treat_stdin () at gzip.c:646

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

StacktraceTop:__read_nocancel () from /lib/libc.so.6
read_buffer (fd=0, buf=0x631dc0, cnt=32768) at util.c:157
fill_inbuf (eof_ok=1) at util.c:125
get_method (in=0) at gzip.c:1244
treat_stdin () at gzip.c:646

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

StacktraceTop:__read_nocancel () from /lib/libc.so.6
read_buffer (fd=0, buf=0x631dc0, cnt=32768) at util.c:157
fill_inbuf (eof_ok=1) at util.c:125
get_method (in=0) at gzip.c:1244
treat_stdin () at gzip.c:646

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

StacktraceTop:__read_nocancel () from /lib/libc.so.6
read_buffer (fd=0, buf=0x631dc0, cnt=32768) at util.c:157
fill_inbuf (eof_ok=1) at util.c:125
get_method (in=0) at gzip.c:1244
treat_stdin () at gzip.c:646

Martin Pitt (pitti)
description: updated
Revision history for this message
Martin Pitt (pitti) wrote :

Reopening for auto-retracer test.

Changed in gzip:
status: Rejected → Unconfirmed
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:__read_nocancel () from /lib/libc.so.6
read_buffer (fd=0, buf=0x631dc0, cnt=32768) at util.c:157
fill_inbuf (eof_ok=1) at util.c:125
get_method (in=0) at gzip.c:1244
treat_stdin () at gzip.c:646

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Martin Pitt (pitti)
Changed in gzip:
status: Unconfirmed → Rejected
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

no comment

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

StacktraceTop:?? ()
?? ()
?? () from /usr/lib/python2.5/site-packages/btctl.so
?? ()
PyArg_ParseTupleAndKeywords (args=0xb781723c, keywords=0xbfd1f234, format=0xbfd1f234 "�32�", kwlist=0xbfd1f240) at ../Python/getargs.c:1251

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Martin Pitt (pitti) wrote : subj

text text

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

arbitrary comment
here.

StacktraceTop:This is an invalid test StacktraceTop
Yes, Really!
foo

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

StacktraceTop:close () from /lib/libc.so.6
?? ()

Changed in gzip:
status: Rejected → Unconfirmed
Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

StacktraceTop:close () from /lib/libc.so.6
?? ()

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:close () from /lib/libc.so.6
?? ()

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

StacktraceTop:close () from /lib/libc.so.6
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Martin Pitt (pitti) wrote : Attach big file

text

Revision history for this message
Martin Pitt (pitti) wrote :

text

Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #1. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem in a dependent package.

Revision history for this message
Martin Pitt (pitti) wrote :

Was just a test bug.

Changed in gzip:
status: New → Invalid
Revision history for this message
Markus Korn (thekorn) wrote : Symbolic stack trace

arbitrary comment
here.

StacktraceTop:This is an invalid test StacktraceTop
Yes, Really!
foo

Revision history for this message
Markus Korn (thekorn) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #1. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

description: updated
Revision history for this message
Aquarion (nicholas-aquarionics) wrote :

Er, with sufficient due respect, what has this to do with bug #1?

Revision history for this message
Markus Korn (thekorn) wrote : Symbolic stack trace

arbitrary comment
here.

StacktraceTop:This is an invalid test StacktraceTop
Yes, Really!
foo

Revision history for this message
Markus Korn (thekorn) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #1. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

Revision history for this message
Daniel Holbach (dholbach) wrote : Symbolic stack trace

arbitrary comment
here.

StacktraceTop:This is an invalid test StacktraceTop
Yes, Really!
foo

Revision history for this message
Daniel Holbach (dholbach) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #1. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Martin and Daniel, please use staging.launchpad.net for test purposes. If you need something that staging can't provide (such as e-mail notifications), talk with Kiko about your needs.

Also, bug 1 currently has 138 subscribers, some of whom represent mailing lists. And a couple of bugs in Launchpad cause bug subscribers to receive more e-mail notifications about duplicates than they should. So if you must use production for tests involving duplicates, please use a second bug report of your own, not bug 1.

Revision history for this message
Martin Pitt (pitti) wrote :
Martin Pitt (pitti)
Changed in gzip:
status: Invalid → New
Revision history for this message
Martin Pitt (pitti) wrote : Crash report cannot be processed

not properly frobnicated

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

Other bug subscribers

Remote bug watches

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