anjuta crashed with SIGSEGV in g_slice_alloc()

Bug #209738 reported by Kevin Williams
6
Affects Status Importance Assigned to Milestone
anjuta (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: anjuta

Just installed Anjuta 2.4.0-2 this morning & it crashed just after I had it create a generic Python project. This is on up-to-date Hardy.

ProblemType: Crash
Architecture: i386
Date: Mon Mar 31 10:31:05 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/anjuta
NonfreeKernelModules: nvidia
Package: anjuta 2:2.4.0-2
PackageArchitecture: i386
ProcCmdline: anjuta
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: anjuta
StacktraceTop:
 g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 gdk_region_rectangle () from /usr/lib/libgdk-x11-2.0.so.0
 gdk_window_invalidate_maybe_recurse ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? ()
Title: anjuta crashed with SIGSEGV in g_slice_alloc()
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev sambashare scanner video

Tags: apport-crash
Revision history for this message
Kevin Williams (bthylafh) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__gdk_region_rectangle (rectangle=0xbf898d80)
IA__gdk_window_invalidate_maybe_recurse (window=0x8369318,
gtk_widget_invalidate_widget_windows (widget=0x80c2150,
gtk_widget_queue_shallow_draw (widget=0x80c2150)
IA__gtk_widget_queue_resize (widget=0x80c2150)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in anjuta:
importance: Undecided → Medium
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. This has already been reported as bug #209561.

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.