Bug 680171 - Spicec got SIGSEGV after qemu-kvm crash
Summary: Spicec got SIGSEGV after qemu-kvm crash
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-client
Version: 6.1
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Uri Lublin
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-24 14:33 UTC by David Jaša
Modified: 2011-08-30 14:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-30 14:56:23 UTC
Target Upstream Version:

Attachments (Terms of Use)
backtrace (7.42 KB, text/plain)
2011-02-24 14:33 UTC, David Jaša 		no flags Details
full backtrace (18.92 KB, text/plain)
2011-02-24 14:35 UTC, David Jaša 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description David Jaša 2011-02-24 14:33:25 UTC 
Description of problem:
When qemu-kvm crashed (bug #680114), spicec has segfaulted instead of graceful exit

Version-Release number of selected component (if applicable):
spice-client-0.7.3-1.el6.x86_64

How reproducible:
didn't try to reproduce

Additional info:

CLI:
$ spicec -h localhost -p 3001
Warning: no factory for 8
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])
Comment 1 David Jaša 2011-02-24 14:33:54 UTC 
Created attachment 480771 [details]
backtrace
Comment 2 David Jaša 2011-02-24 14:35:39 UTC 
Created attachment 480772 [details]
full backtrace
Comment 4 Brock Organ 2011-03-01 14:43:13 UTC 
Reporter,

Could I please ask you to provide a priority assessment (set the priority field to one of urgent/high/medium/low) for the impact of this issue?  This will help us prioritize this issue with our other outstanding bugs for the current release cycle ...

Regards,

Brock
Comment 10 David Jaša 2011-08-30 14:56:23 UTC 
Didn't observe the bug for quite some time, closing as CURRENTRELEASE
Note You need to log in before you can comment on or make changes to this bug.