crashed with SIGSEGV in calloc()

Bug #627939 reported by Krzysztof Matusik on 2010-09-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)

Bug Description

Binary package hint: virt-manager

Happens randomly when clicking virtmanager GUI.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: virt-manager 0.8.4-3ubuntu6
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 1 11:20:43 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/share/virt-manager/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: python /usr/share/virt-manager/
 Segfault happened at: 0x7fc9799f062f: mov 0x8(%rcx),%rsi
 PC (0x7fc9799f062f) ok
 source "0x8(%rcx)" (0xe001800200000008) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: virt-manager
 ?? () from /lib/
 calloc () from /lib/
 g_malloc0 () from /lib/
 ?? () from /lib/
 ?? () from /lib/
Title: crashed with SIGSEGV in calloc()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare tape video

visibility: private → public

 _int_malloc (av=0x7fc979cf4e40, bytes=1536) at malloc.c:4528
 __libc_calloc (n=<value optimized out>,
 g_main_loop_run (loop=0x600)
 ?? ()
 ?? ()

Changed in virt-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Marc Deslauriers (mdeslaur) wrote :

Thanks for reporting this issue.

Can you reproduce this issue with gtk-vnc 0.4.1-3ubuntu1?
(the binary packages are called libgtk-vnc-1.0-0 and python-gtk-vnc)

Changed in virt-manager (Ubuntu):
status: New → Incomplete

It was quite tricky- I can't tell exactly what was I doing when it happend, so I'll just be using this and report back if anything happens.

Marc Deslauriers (mdeslaur) wrote :

OK, this probably got fixed in the gtk-vnc update.

I'll close this bug. Feel free to reopen a new one if the problem comes back.

Changed in virt-manager (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers