Bug #416
closedBLAST fails on the example in which the LDV_ERROR label and ldv_main are defined in different files
0%
Description
rcv-blast: NORMAL: Running BLAST with alias analysis (this may take longer). rcv-blast: NORMAL: Running BLAST for drivers/tests-envgen/test-twomains-mutex/twomains.ko, entry ldv_main1_plain_sorted_withcheck... rcv-blast: INFO: /home/mutilin/opt/ldv/bin/../shared/sh/timeout -m 1000000 -t 900 pblast.opt /home/mutilin/temp/ldv-tools-test/test-envmodels/launcher-working-dir/ldv-manager-work-dir/work/current--X--tests-envgen--test-twomains-mutex.tar.bz2--X--defaultmykernel-1-2.6.32.15--X--32_1/mykernel-1-2.6.32.15/csd_deg_dscv/0/dscv_tempdir/dscv/cmdfiles/rcv/32_1/preprocessed/drivers-tests-envgen-test-twomains-mutex-main1_mod.c.common.i /home/mutilin/temp/ldv-tools-test/test-envmodels/launcher-working-dir/ldv-manager-work-dir/work/current--X--tests-envgen--test-twomains-mutex.tar.bz2--X--defaultmykernel-1-2.6.32.15--X--32_1/mykernel-1-2.6.32.15/csd_deg_dscv/0/dscv_tempdir/dscv/cmdfiles/rcv/32_1/preprocessed/drivers-tests-envgen-test-twomains-mutex-main2_obj.i -predH 7 -craig 2 -ignoredupfn -nosserr -main ldv_main1_plain_sorted_withcheck -L LDV_ERROR -cldepth 0 -alias bdd -cref -nomusts -const -devdebug BLAST couldn't find entry point/error location at /home/mutilin/opt/ldv/bin/../dscv/rcv/blast line 285. at /home/mutilin/opt/ldv/bin/../dscv/rcv/blast line 90 at /home/mutilin/opt/ldv/bin/../dscv/rcv/blast line 90 rcv-blast: INFO: BLAST debug trace is being written to /home/mutilin/temp/ldv-tools-test/test-envmodels/launcher-working-dir/ldv-manager-work-dir/work/current--X--tests-envgen--test-twomains-mutex.tar.bz2--X--defaultmykernel-1-2.6.32.15--X--32_1/mykernel-1-2.6.32.15/csd_deg_dscv/0/dscv_tempdir/dscv/cmdfiles/rcv/32_1/reports/drivers/tests-envgen/test-twomains-mutex/twomains.ko.ldv_main1_plain_sorted_withcheck.debug.gz rcv-blast: TRACE: BLAST open3 return value: 768 rcv-blast: INFO: BLAST return value: 768 rcv-blast: TRACE: BLAST stats: utime 0.97206, stime 0.144009
Files
Updated by Vadim Mutilin about 14 years ago
- File drivers-tests-envgen-test-twomains-mutex-main2_obj.i drivers-tests-envgen-test-twomains-mutex-main2_obj.i added
- File drivers-tests-envgen-test-twomains-mutex-main1_mod.c.common.i drivers-tests-envgen-test-twomains-mutex-main1_mod.c.common.i added
- File twomains.ko.ldv_main1_plain_sorted_withcheck.debug.gz twomains.ko.ldv_main1_plain_sorted_withcheck.debug.gz added
Updated by Pavel Shved about 14 years ago
BLAST fails if the LDV_ERROR label and ldv_main are defined in different files
This is a lie.
Updated by Vadim Mutilin about 14 years ago
- Subject changed from BLAST fails if the LDV_ERROR label and ldv_main are defined in different files to BLAST fails on the example in which the LDV_ERROR label and ldv_main are defined in different files
- Priority changed from Normal to High
Awful truth :)
Rising to High because Small test set fails and prevents pushing new version of envgen into master
Updated by Pavel Shved about 14 years ago
- File a.c a.c added
- File b.c b.c added
- Due date set to 09/07/2010
- Category set to BLAST
- Status changed from New to Open
- Priority changed from High to Immediate
- Estimated time set to 2.00 h
Вадим Мутилин wrote:
Awful truth :)
Vadim, please, create a couple of source code files (or check the ones I've attached) and stop insisting on an issue that has nothing to do with the problem.
Rising to High because Small test set fails and prevents pushing new version of envgen into master
That's not "High", that's "Immediate". I'll address these bugs today.
Updated by Vadim Mutilin about 14 years ago
Pavel Shved wrote:
Вадим Мутилин wrote:
Vadim, please, create a couple of source code files (or check the ones I've attached) and stop insisting on an issue that has nothing to do with the problem.
The issue is that there is an error, and I'm not insisting that the cause is main and label placed in different files. On such examples BLAST has worked before and is working now even in small tests. Moreover, I suspect that the error caused by recent changes in envgen. The title just describes the example tests-envgen-test-twomains-mutex and it is not a lie :) I changed it to be the truth.
Updated by Pavel Shved about 14 years ago
- Status changed from Open to Closed
I found the issue. The thing is that BLAST indeed doesn't find the main you specified (ldv_main1_plain_sorted_withcheck).
But this main does present in main_2.obj.i file! What's the matter?
When parsing this function, CIL found that the label ldv_module_exit was "goto-ed" but was not specified. This led to "Error" at 111th line, as you can see in the trace you attached. The possible consequence of this is that BLAST didn't add the function to the "global function table", and thus it wasn't found during the entry point lookup. Hence the error.
The bug about this incorrect way of generating the model is #422.