Bug 677134 - [abrt] vala-0.10.2-1.fc14: Process /usr/bin/valac-0.10 was killed by signal 11 (SIGSEGV)
Summary: [abrt] vala-0.10.2-1.fc14: Process /usr/bin/valac-0.10 was killed by signal 1...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: vala
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michel Alexandre Salim
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a8c7a2e5f9504c5c34d24e0c2da...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-13 15:51 UTC by Lee Dan
Modified: 2012-06-04 14:50 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-04 14:50:58 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (17.69 KB, text/plain)
2011-02-13 15:51 UTC, Lee Dan 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Lee Dan 2011-02-13 15:51:48 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/valac --pkg=posix --pkg=gtk+-2.0 -g -C src/systemadm.vala src/systemd-interfaces.vala
comment: I tried to compile these files directly like "valac systemadm.vala" and it just show me compile erros. Maybe the code need a later version compiler than valac-0.10.
component: vala
crash_function: vala_data_type_get_actual_type
executable: /usr/bin/valac-0.10
kernel: 2.6.35.10-74.fc14.i686
package: vala-0.10.2-1.fc14
rating: 4
reason: Process /usr/bin/valac-0.10 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1297610925
uid: 500

How to reproduce
-----
1. sync systemd code at Feb 12 2011
2. ./autogen.sh && make
3. it crashes when comiple the vala files.
Comment 1 Lee Dan 2011-02-13 15:51:52 UTC 
Created attachment 478484 [details]
File: backtrace
Comment 2 Michel Alexandre Salim 2012-06-04 14:50:58 UTC 
Release is no longer supported. FWIW it seems that Vala in later Fedora releases no longer triggers abrt crashes
Note You need to log in before you can comment on or make changes to this bug.