Bug 770819 - [abrt] crossvc-1.5.2-7.fc12: vsnprintf: Process /usr/lib/CrossVC/crossvc.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] crossvc-1.5.2-7.fc12: vsnprintf: Process /usr/lib/CrossVC/crossvc.bin ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: crossvc
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jochen Schmitt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b9ee7f31f8718c9034026b49f3a...
: 751973 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-29 10:42 UTC by Mandar
Modified: 2012-06-13 19:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-13 19:11:53 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (42.57 KB, text/plain)
2011-12-29 10:42 UTC, Mandar 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Mandar 2011-12-29 10:42:41 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 43596 bytes
cmdline: /usr/lib/CrossVC/crossvc.bin
comment: Is there any solution?
component: crossvc
Attached file: coredump, 4157440 bytes
crash_function: vsnprintf
executable: /usr/lib/CrossVC/crossvc.bin
kernel: 2.6.35.14-103.fc14.i686
package: crossvc-1.5.2-7.fc12
rating: 4
reason: Process /usr/lib/CrossVC/crossvc.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1325155260
uid: 502

How to reproduce
-----
1.  whenever try to open it get crash
2.
3.
Comment 1 Mandar 2011-12-29 10:42:45 UTC 
Created attachment 549934 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 16:34:56 UTC 
*** Bug 751973 has been marked as a duplicate of this bug. ***
Comment 3 Jochen Schmitt 2012-06-13 19:11:53 UTC 
Because this bug was reported agains Fedora 14 is will close it. Fedora 14 is 
EOL. So please update to a more recent release of Fedora. After the update
you can check out it the reported bug still exist and recreate a new ticker
if so.
Note You need to log in before you can comment on or make changes to this bug.