pan crashed with SIGSEGV in malloc()

Bug #469484 reported by Graeme Glass
This bug affects 3 people
Affects Status Importance Assigned to Milestone
pan (Ubuntu)

Bug Description

Binary package hint: pan

Just loaded up list of groups and it crashed

ProblemType: Crash
Architecture: i386
Date: Sun Nov 1 23:04:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pan
Package: pan 0.133-1ubuntu1
ProcCmdline: pan
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 11
SourcePackage: pan
 ?? () from /lib/tls/i686/cmov/
 malloc () from /lib/tls/i686/cmov/
 operator new(unsigned int) () from /usr/lib/
 std::vector<int, std::allocator<int> >::_M_insert_aux(__gnu_cxx::__normal_iterator<int*, std::vector<int, std::allocator<int> > >, int const&) ()
 PanTreeStore::get_path(PanTreeStore::Row const*) const ()
Title: pan crashed with SIGSEGV in malloc()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
 Segfault happened at: 0x9e9379: call 0x99298f
 PC (0x009e9379) ok
 source "0x99298f" (0x0099298f) ok
 destination "(%esp)" (0xbef43fbc) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA

Revision history for this message
Graeme Glass (graemeglass) wrote :
Revision history for this message
souplin (klage) wrote :

same here. Can be reproduced by minimizing the group list and afterwards clicking on the arrow to maximize. Pan crashes:

pan[4440]: segfault at befb5fa8 ip 00d3d379 sp befb5fac error 6 in[cd0000+13e000]

Kees Cook (kees)
description: updated
tags: added: stack-exhaustion
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pan (Ubuntu):
status: New → Confirmed
Revision history for this message
oldrocker99 (fhwri99) wrote :

I was using the filter in the top middle of the screen and it crashed.

Revision history for this message
Mladen Gogala (mgogala) wrote :


To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers