python2.7 crashed with SIGSEGV in __find_specmb()

Bug #1155467 reported by Vsevolod Velichko
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pygobject-2 (Ubuntu)
Invalid
Medium
Unassigned
quickly (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Occures, each time when I used "quickly release". First appeared on quantal with all the updates and remains after distupgrade to raring.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: python2.7-minimal 2.7.3-16ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Fri Mar 15 01:19:09 2013
ExecutablePath: /usr/bin/python2.7
MarkForUpload: True
ProcCmdline: python setup.py install_egg_info -d /tmp/tmpt4Y8EH
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=ru_RU.UTF-8
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7fb90ed818ca <_IO_vfprintf_internal+154>: callq 0x7fb90edcbb30 <strchrnul>
 PC (0x7fb90ed818ca) ok
 source "0x7fb90edcbb30" (0x7fb90edcbb30) ok
 destination "(%rsp)" (0x7fffa1101fa0) 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: python2.7 crashed with SIGSEGV in g_type_get_qdata()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Vsevolod Velichko (torkvemada) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __find_specmb (format=0x7fb90d40166a <Address 0x7fb90d40166a out of bounds>) at printf-parse.h:109
 _IO_vfprintf_internal (s=s@entry=0x7fffa11025f0, format=format@entry=0x7fb90d40166a <Address 0x7fb90d40166a out of bounds>, ap=ap@entry=0x7fffa1102818) at vfprintf.c:1326
 __GI___vasprintf_chk (result_ptr=0x7fffa1102738, flags=1, format=0x7fb90d40166a <Address 0x7fb90d40166a out of bounds>, args=0x7fffa1102818) at vasprintf_chk.c:66
 ?? ()
 ?? ()

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 python2.7 (Ubuntu):
importance: Undecided → Medium
summary: - python2.7 crashed with SIGSEGV in g_type_get_qdata()
+ python2.7 crashed with SIGSEGV in __find_specmb()
tags: removed: need-amd64-retrace
Revision history for this message
Matthias Klose (doko) wrote :

which egg did you try to install?

affects: python2.7 (Ubuntu) → pygobject (Ubuntu)
information type: Private → Public
Revision history for this message
Vsevolod Velichko (torkvemada) wrote :

It was package 'quickly'[1] which command 'quickly release' I used to package and release the 'parcel-tracker', package of mine[2].
[1] https://launchpad.net/ubuntu/+source/quickly
[2] https://code.launchpad.net/~torkvemada/parcel-tracker/quickly_trunk

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

ProcMaps shows that your project is using both the deprecated static Python glib/gobject/gtk bindings, as well as the current gobject-introspection based bindings. I'm afraid you can't use both at the same time, as that will trigger all kinds of crashes in libraries. Please port your project to GI.

affects: pygobject (Ubuntu) → pygobject-2 (Ubuntu)
Changed in pygobject-2 (Ubuntu):
status: New → Invalid
Changed in quickly (Ubuntu):
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.