Displaying 5 results from an estimated 5 matches for "entryloc".
Did you mean:
entry_low
2016 Dec 02
2
Libfuzzer depending on uninitialized debug info
...as the problem.
If it came across as "libfuzzer is evil" that was not my intent, sorry!
No, no, I did not mean you implied that :)
Just wanted to make sure everyone understand that this is not libFuzzer-specific.
Looking at lib/Transforms/Instrumentation/SanitizerCoverage.cpp:
DebugLoc EntryLoc;
if (IsEntryBB) {
if (auto SP = F.getSubprogram())
EntryLoc = DebugLoc::get(SP->getScopeLine(), 0, SP);
...
} else {
EntryLoc = IP->getDebugLoc();
}
IRBuilder<> IRB(&*IP);
IRB.SetCurrentDebugLocation(EntryLoc);
So, using this I assumed that the newly generat...
2016 Dec 02
2
Libfuzzer depending on uninitialized debug info
...ber 01, 2016 5:01 PM
To: Robinson, Paul
Cc: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Libfuzzer depending on uninitialized debug info
Ok...
The particular instance of the problem can be solved with this patch in my code:
+ IRB.SetInsertPoint(Ins);
IRB.SetCurrentDebugLocation(EntryLoc);
- IRB.SetInsertPoint(Ins);
(apparently, SetInsertPoint invalidates the previous call to SetCurrentDebugLocation)
But then there is another problem....
% cat dummy.c
void foo() {}
% clang -O -c -gmlt -fsanitize-coverage=func,trace-pc-guard -S dummy.c -o -
.LBB0_1:
.loc 1 1 0...
2016 Dec 01
2
Libfuzzer depending on uninitialized debug info
It might be a wider problem than libfuzzer. I did want to raise the problem asap and libfuzzer is something we know has the problem.
If it came across as "libfuzzer is evil" that was not my intent, sorry!
--paulr
From: Kostya Serebryany [mailto:kcc at google.com]
Sent: Thursday, December 01, 2016 2:53 PM
To: Robinson, Paul
Cc: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev]
2016 Dec 03
0
Libfuzzer depending on uninitialized debug info
...bject:* Re: [llvm-dev] Libfuzzer depending on uninitialized debug info
>
>
>
> Ok...
>
>
>
> The particular instance of the problem can be solved with this patch in my
> code:
>
>
>
> + IRB.SetInsertPoint(Ins);
>
> IRB.SetCurrentDebugLocation(EntryLoc);
>
> - IRB.SetInsertPoint(Ins);
>
>
>
> (apparently, SetInsertPoint invalidates the previous call to
> SetCurrentDebugLocation)
>
>
>
> But then there is another problem....
>
>
>
> % cat dummy.c
>
> void foo() {}
>
>
>
> % clang...
2016 Dec 12
1
Libfuzzer depending on uninitialized debug info
...c: llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
Subject: Re: [llvm-dev] Libfuzzer depending on uninitialized debug info
Ok...
The particular instance of the problem can be solved with this patch in my code:
+ IRB.SetInsertPoint(Ins);
IRB.SetCurrentDebugLocation(EntryLoc);
- IRB.SetInsertPoint(Ins);
(apparently, SetInsertPoint invalidates the previous call to SetCurrentDebugLocation)
But then there is another problem....
% cat dummy.c
void foo() {}
% clang -O -c -gmlt -fsanitize-coverage=func,trace-pc-guard -S dummy.c -o -
.LBB0_1:
.loc 1 1 0...