Actions
Bug #4395
closedInternal compiler errors of Aspectator
Start date:
07/27/2013
Due date:
% Done:
0%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
eec536a
Description
This is a collection of such the issues.
Files
Updated by Ilya Shchepetkov over 11 years ago
- File segfault.tar.xz segfault.tar.xz added
19 more examples of such errors are in the attached file.
Updated by Evgeny Novikov over 11 years ago
For examples from the attached file on commit df9bb68 of the bug-4395 branch (aspectator submodule) I have:
- arp_tables.c.macroinstrumented - Ok.
- cfg80211.c.macroinstrumented - Ok.
- debug.c.macroinstrumented - Ok.
- debugfs.c.macroinstrumented - Ok.
- do_balan.c.macroinstrumented - #4399 (this is a C file of fs/reiserfs/reiserfs.ko module).
- emulate.c.macroinstrumented - #4398.
- fs.c.macroinstrumented - strange thing instead of:
static const char objtree[] = OBJTREE;
there is:static const char objtree[] = /home/shchepetkov/1 -3.11-rc1;
and the same for:static const char srctree[] = SRCTREE;
It is interesting but in reference launches almost all modules from the kernel directory aren't verified. So that we didn't see this error before. - fw.c.macroinstrumented - Ok.
- g_ffs.c.macroinstrumented - Ok (it includes f_fs.c that had segfault before #4396).
- interrupt.c.macroinstrumented - Ok.
- ip6_tables.c.macroinstrumented - Ok.
- ip_tables.c.macroinstrumented - Ok.
- main.c.macroinstrumented - Ok.
- mmu.c.macroinstrumented - Ok.
- netdev.c.macroinstrumented - Ok.
- pcie_bus.c.macroinstrumented - Ok.
- trace.c.macroinstrumented - Ok.
- txrx.c.macroinstrumented - Ok.
- wmi.c.macroinstrumented - Ok.
Updated by Evgeny Novikov over 11 years ago
Updated by Evgeny Novikov about 11 years ago
- Status changed from Open to Closed
- Published in build set to eec536a
Fixed in eec536a. CIF submodule was updated in commit:df9ad40 of LDV tools.
After the fix I gained quite positive changes in verification results for the launch on the whole kernel against 32_7a rule model:- 23 Unknown → Safe.
- 2 Unknown → Unsafe. Both looks to be False positives. So I would like to wait until we will get results during following reference launches on 3.12-rc1 and just then mark up them.
And there is no more Segmentation faults of Aspectator!
Actions