ipython3 crashed with SIGSEGV in gtk_style_context_get_valist()

Bug #1046311 reported by Dimitri John Ledkov
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gobject-introspection (Ubuntu)
Invalid
Low
Unassigned
ipython (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I was prototyping using gi.repository.
Obviously I did something that gtk didn't like and it segvaulted. Not sure why a crash is being reported though.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: ipython3 0.13-1
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Wed Sep 5 13:24:10 2012
ExecutablePath: /usr/bin/ipython3
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python3.2mu
PackageArchitecture: all
ProcCmdline: python3 /usr/bin/ipython3
ProcEnviron:
 TERM=xterm-256color
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
SegvAnalysis:
 Segfault happened at: 0x7ff1116f72d7 <gtk_style_context_get_valist+215>: mov 0x30(%rax),%rdx
 PC (0x7ff1116f72d7) ok
 source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ipython
StacktraceTop:
 gtk_style_context_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_style_context_get () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_style_context_get_color () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: ipython3 crashed with SIGSEGV in gtk_style_context_get_valist()
UpgradeStatus: Upgraded to quantal on 2012-01-04 (244 days ago)
UserGroups: adm admin cdrom dialout kvm libvirtd lp lpadmin plugdev sambashare sbuild vboxusers

Revision history for this message
Dimitri John Ledkov (xnox) wrote :
Changed in ipython (Ubuntu):
status: New → Invalid
Changed in gobject-introspection (Ubuntu):
status: New → Confirmed
importance: Undecided → Low
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x00007ff1116f72d7 in ?? ()
 #1 0x0000000002a64c80 in ?? ()
 #2 0x0000000002a48df0 in ?? ()
 #3 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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 gobject-introspection (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libgirepository-1.0-1: package version 1.33.10-1 dbgsym version 1.33.9-1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

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.