Bug #1166: GCC-aspectator fails with fatal error: incorrect exceptional code - C Instrumentation Framework - Open-Source Projects

Actions

Copy link

Bug #1166

closed

GCC-aspectator fails with fatal error: incorrect exceptional code

Added by Pavel Shved over 13 years ago. Updated about 12 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Evgeny Novikov

Category:

Start date:

05/03/2011

Due date:

% Done:

Estimated time:

Detected in build:

svn

Platform:

Published in build:

Description

Steps to reproduce:

LDV_DEBUG=30 ldv-manager rule_models=32_1a "envs=linux-2.6.31.6.tar.bz2" drivers=drivers/mtd/chips/cfi_probe.ko kernel_driver=1 name=ri14

The error message is:

/home/pavel/work/ldv/test/work/current--X--drivers/mtd/chips/cfi_probe.ko--X--ri14linux-2.6.31.6--X--32_1a/linux-2.6.31.6/csd_deg_dscv/11/dscv_tempdir/dscv/ri/32_1a/drivers/mtd/chips/cfi_probe.c.p: In function 'ldv_main0_sequence_infinite_withcheck_stateful':
/home/pavel/work/ldv/test/work/current--X--drivers/mtd/chips/cfi_probe.ko--X--ri14linux-2.6.31.6--X--32_1a/linux-2.6.31.6/csd_deg_dscv/11/dscv_tempdir/dscv/ri/32_1a/drivers/mtd/chips/cfi_probe.c.p:549:18: error: storage size of 'var_group2' isn't known
/home/pavel/work/ldv/test/work/current--X--drivers/mtd/chips/cfi_probe.ko--X--ri14linux-2.6.31.6--X--32_1a/linux-2.6.31.6/csd_deg_dscv/11/dscv_tempdir/dscv/ri/32_1a/drivers/mtd/chips/cfi_probe.c.p:613:2: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
/home/pavel/work/ldv/test/work/current--X--drivers/mtd/chips/cfi_probe.ko--X--ri14linux-2.6.31.6--X--32_1a/linux-2.6.31.6/csd_deg_dscv/11/dscv_tempdir/dscv/ri/32_1a/drivers/mtd/chips/cfi_probe.c.p:549:28: warning: unused variable 'var_group2' [-Wunused-variable]
/home/pavel/work/ldv/test/work/current--X--drivers/mtd/chips/cfi_probe.ko--X--ri14linux-2.6.31.6--X--32_1a/linux-2.6.31.6/csd_deg_dscv/11/dscv_tempdir/dscv/ri/32_1a/drivers/mtd/chips/cfi_probe.c.p:790:1: fatal error: incorrect exceptional code

In other cases the "incorrect exceptional code" error is also preceded with a compile error (for instance, for the famous jedec_probe bug #553)

Related issues 3 (3 open — 0 closed)

Actions

Copy link

Updated by Pavel Shved over 13 years ago

There are only 9 drivers affected by this issue. Not that important, I guess.

Actions

Copy link

Updated by Evgeny Novikov over 13 years ago

Status changed from New to Open

As well as #1158.

Actions

Copy link

Updated by Evgeny Novikov over 13 years ago

Status changed from Open to Closed

After partial implementation of #970 issue it becomes clear that the only error_mark tree node isn't processed. In fact this means that a given driver isn't compilable with gcc 4.6.0 by some reasons. I have investigated these reasons and I'm going to create special bugs for them.

Actions

Copy link