pydoc2.7 crashed with SIGSEGV in g_type_get_qdata()

Bug #921383 reported by Pi Delport
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PyGTK
New
Undecided
Unassigned
python2.7 (Ubuntu)
New
Medium
Unassigned

Bug Description

This happens while attempting pydoc -k.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: python2.7 2.7.2-5ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Jan 24 12:45:53 2012
ExecutablePath: /usr/bin/pydoc2.7
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python2.7 /usr/bin/pydoc -k yaml
SegvAnalysis:
 Segfault happened at: 0x7f39f50dd58b <vfprintf+155>: callq 0x7f39f5121e60 <strchrnul>
 PC (0x7f39f50dd58b) ok
 source "0x7f39f5121e60" (0x7f39f5121e60) ok
 destination "(%rsp)" (0x7ffff69d4f70) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
 g_type_get_qdata () from /usr/lib/x86_64-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
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
Title: pydoc2.7 crashed with SIGSEGV in g_type_get_qdata()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: admin

Revision history for this message
Pi Delport (pi-delport) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_get_qdata (type=<optimized out>, quark=55) at /build/buildd/glib2.0-2.30.0/./gobject/gtype.c:3668
 pygobject_lookup_class (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:905
 pygobject_lookup_class (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:894
 pyg_type_get_bases (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:659
 pygobject_new_with_interfaces (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:702

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 python2.7 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pi Delport (pi-delport) wrote :

This looks like an "assertion failed" debug print:

#0 __find_specmb (format=0x7f39f1f40732 "%s: assertion `%s' failed") at printf-parse.h:99

is causing unbounded recursion involving the following loop:

...
#10 pygobject_lookup_class (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:894
#11 0x00007f39e88b9032 in pyg_type_get_bases (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:659
#12 0x00007f39e88b90e2 in pygobject_new_with_interfaces (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:702
#13 0x00007f39e88b8fe5 in pygobject_lookup_class (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:913
#14 pygobject_lookup_class (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:894
...

Revision history for this message
Pi Delport (pi-delport) wrote :

The last line output just before the segfault:

...
** (python2.7:8669): CRITICAL **: pyg_register_boxed: assertion `boxed_type != 0' failed

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.