reportbug crashed with SIGSEGV

Bug #1049108 reported by Alex
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
reportbug (Ubuntu)
New
Medium
Unassigned

Bug Description

When attempting to file a new bug against the wnpp package (the fake package for requesting new packages) using the graphical interface, reportbug SIGSEGVed straight after selecting the wnpp package.

Please let me know if you want me to perform any actions to help get you extra information.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: reportbug 6.4.3ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Tue Sep 11 14:04:35 2012
ExecutablePath: /usr/bin/reportbug
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/reportbug -B debian
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
SegvAnalysis:
 Segfault happened at: 0x7ff662125c44: mov (%rax,%rsi,4),%al
 PC (0x7ff662125c44) ok
 source "(%rax,%rsi,4)" (0xaaaaaaaaaaaaab26) not located in a known VMA region (needed readable region)!
 destination "%al" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: reportbug
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
Title: reportbug crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Alex (alex.b) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 can_break_at (layout=0x7ff650491420, offset=31, always_wrap_char=0) at /build/buildd/pango1.0-1.30.1/./pango/pango-layout.c:3089
 can_break_in (allow_break_at_start=<optimized out>, num_chars=47, start_offset=<optimized out>, layout=0x7ff650491420) at /build/buildd/pango1.0-1.30.1/./pango/pango-layout.c:3106
 process_line (state=0x7ff65a64dcd0, layout=0x7ff650491420) at /build/buildd/pango1.0-1.30.1/./pango/pango-layout.c:3597
 pango_layout_check_lines (layout=0x7ff650491420) at /build/buildd/pango1.0-1.30.1/./pango/pango-layout.c:3913
 pango_layout_check_lines (layout=0x7ff650491420) at /build/buildd/pango1.0-1.30.1/./pango/pango-layout.c:3788

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in reportbug (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
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.