help() modules crashes with SIGSEGV in apt_pkg.so

Bug #905577 reported by Dave Morley
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
python-apt (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I got the crash by opening ipython and running help() once in the interactive help I typed in modules, there were a couple of errors show up in the shell but then it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ipython 0.11-2
ProcVersionSignature: Ubuntu 3.2.0-5.11-generic 3.2.0-rc5
Uname: Linux 3.2.0-5-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Sat Dec 17 00:30:02 2011
ExecutablePath: /usr/bin/ipython
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111212)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/bin/ipython
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
SegvAnalysis:
 Segfault happened at: 0x5421f9 <vfprintf+201>: movl $0x25,0x4(%esp)
 PC (0x005421f9) ok
 source "$0x25" ok
 destination "0x4(%esp)" (0xbf28bfa0) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: ipython
StacktraceTop:
 g_return_if_fail_warning () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_type_get_qdata () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
Title: ipython crashed with SIGSEGV in g_return_if_fail_warning()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Dave Morley (davmor2) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __find_specmb (format=0xbe175a <Address 0xbe175a out of bounds>) at printf-parse.h:99
 _IO_vfprintf_internal (s=0x6bdc98, format=0x6bb343 <Address 0x6bb343 out of bounds>, ap=0x28 <Address 0x28 out of bounds>) at vfprintf.c:1325
 __GI___vasprintf_chk (result_ptr=0xbf28c64c, flags=1, format=0xbe175a <Address 0xbe175a out of bounds>, args=0xbf28cb0c "\230\334k") at vasprintf_chk.c:68
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in ipython (Ubuntu):
importance: Undecided → Medium
summary: - ipython crashed with SIGSEGV in g_return_if_fail_warning()
+ ipython crashed with SIGSEGV in __find_specmb()
tags: removed: need-i386-retrace
Revision history for this message
Julian Taylor (jtaylor) wrote :

this is not a ipython issue, but help(), modules attempts to import all modules and crashes in one of them.
for me it crashes in python-apt:

gdb /usr/bin/python-dbg
(gdb) r
>> help()
>>> modules
Program received signal SIGSEGV, Segmentation fault.
(gdb) bt
#0 0x0000000000018236 in ?? ()
#1 0x00007fffefd006e1 in initapt_pkg () from /usr/lib/python2.7/dist-packages/apt_pkg.so
#2 0x000000000054778d in _PyImport_LoadDynamicModule (name=0x7fffffff5794 "apt_pkg", pathname=
    0x7fffffff46a0 "/usr/lib/python2.7/dist-packages/apt_pkg.so", fp=0x266f200)
    at ../Python/importdl.c:53
#3 0x0000000000543734 in load_module (name=0x7fffffff5794 "apt_pkg", fp=0x266f200, pathname=
    0x7fffffff46a0 "/usr/lib/python2.7/dist-packages/apt_pkg.so", type=3, loader=0x0)
    at ../Python/import.c:1834
#4 0x0000000000545940 in import_submodule (mod=None, subname=0x7fffffff5794 "apt_pkg", fullname=
    0x7fffffff5794 "apt_pkg") at ../Python/import.c:2596

affects: ipython (Ubuntu) → python-apt (Ubuntu)
Changed in python-apt (Ubuntu):
status: New → Confirmed
summary: - ipython crashed with SIGSEGV in __find_specmb()
+ help() modules crashes with SIGSEGV in apt_pkg.so
visibility: private → public
Revision history for this message
Julian Andres Klode (juliank) wrote :

The reported bug was for python-gobject, but the comment by Julian Taylor is a different issue, in apt_pkg.

Probably should reassign this one to pygobject, and then either open a new one for python-apt or close it (there are not enough information [line number] to debug this anyway).

What's preferred?

Changed in python-apt (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for python-apt (Ubuntu) because there has been no activity for 60 days.]

Changed in python-apt (Ubuntu):
status: Incomplete → Expired
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.