Re: Issue 25514 in oss-fuzz: qemu: Coverage build failure

Re: Issue 25514 in oss-fuzz: qemu: Coverage build failure

[Paolo Bonzini]

On 21/09/20 12:10, ClusterFuzz-External via monorail wrote:
> 
> Comment #2 on issue 25514 by ClusterFuzz-External: qemu: Coverage build
> failure
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25514#c2
> 
> Friendly reminder that the the build is still failing.
> Please try to fix this failure to ensure that fuzzing remains productive.
> Latest build log:
> https://oss-fuzz-build-logs.storage.googleapis.com/log-632125f2-e66b-4480-9504-c1097198069a.txt
> 
> -- 
> You received this message because:
> 1. You were specifically CC'd on the issue
> 
> You may adjust your notification preferences at:
> https://bugs.chromium.org/hosting/settings
> 
> Reply to this email to add a comment.

It's now failing with:

Step #3: /usr/bin/ld: section .interp loaded at
[00000000000002a8,00000000000002c3] overlaps section .data.fuzz_ordered
loaded at [0000000000000000,000000000016ebff]

Do you know what's going on?  Also, should we make
scripts/oss-fuzz/build.sh use "make V=1"?

Paolo

Re: Issue 25514 in oss-fuzz: qemu: Coverage build failure

[Alexander Bulekov]

On 200921 1410, Paolo Bonzini wrote:
> On 21/09/20 12:10, ClusterFuzz-External via monorail wrote:
> > 
> > Comment #2 on issue 25514 by ClusterFuzz-External: qemu: Coverage build
> > failure
> > https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25514#c2
> > 
> > Friendly reminder that the the build is still failing.
> > Please try to fix this failure to ensure that fuzzing remains productive.
> > Latest build log:
> > https://oss-fuzz-build-logs.storage.googleapis.com/log-632125f2-e66b-4480-9504-c1097198069a.txt
> > 
> > -- 
> > You received this message because:
> > 1. You were specifically CC'd on the issue
> > 
> > You may adjust your notification preferences at:
> > https://bugs.chromium.org/hosting/settings
> > 
> > Reply to this email to add a comment.
> 
> It's now failing with:
> 
> Step #3: /usr/bin/ld: section .interp loaded at
> [00000000000002a8,00000000000002c3] overlaps section .data.fuzz_ordered
> loaded at [0000000000000000,000000000016ebff]
> 
> Do you know what's going on?  Also, should we make
> scripts/oss-fuzz/build.sh use "make V=1"?

Hi Paolo,
These are the builds with clang coverage enabled.
The normal fuzzing builds are succeeding now (log from this morning:
https://oss-fuzz-build-logs.storage.googleapis.com/log-a426424c-cae4-407a-ae7b-205a9ae59286.txt
)

I already send a patch that seems to fix the coverage build failure, but
I can't explain why it does the trick. 
Message-Id: <20200909220516.614222-1-alxndr@bu.edu>
https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg03639.html

-Alex

> 
> Paolo
> 

Re: Issue 25514 in oss-fuzz: qemu: Coverage build failure

[Paolo Bonzini]

On 21/09/20 15:38, Alexander Bulekov wrote:
> Hi Paolo,
> These are the builds with clang coverage enabled.
> The normal fuzzing builds are succeeding now (log from this morning:
> https://oss-fuzz-build-logs.storage.googleapis.com/log-a426424c-cae4-407a-ae7b-205a9ae59286.txt
> )
> 
> I already send a patch that seems to fix the coverage build failure, but
> I can't explain why it does the trick. 
> Message-Id: <20200909220516.614222-1-alxndr@bu.edu>
> https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg03639.html

The reason for the bug is the -Wl,-lm in QEMU_LDFLAGS.  Putting the
tricky flags first actually makes sense, so I'll queue it.

Paolo