You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2019/06/01 00:50:00 UTC

[jira] [Commented] (ARROW-2256) [C++] Fuzzer builds fail out of the box on Ubuntu 16.04 using LLVM apt repos

    [ https://issues.apache.org/jira/browse/ARROW-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853514#comment-16853514 ] 

Wes McKinney commented on ARROW-2256:
-------------------------------------

I can't get fuzzing working at all on Ubuntu 19.04. The error looks like this

{code}
$ ./debug/arrow-ipc-fuzzing-test 
INFO: Seed: 3163524211
INFO: Loaded 1 modules   (33926 guards): 33926 [0xd15918, 0xd36b30), 
INFO: Loaded 1 modules   (143 inline 8-bit counters): 143 [0xd36b30, 0xd36bbf), 
INFO: Loaded 1 PC tables (143 PCs): 143 [0xd36bc0,0xd374b0), 
ERROR: The size of coverage PC tables does not match the
number of instrumented PCs. This might be a compiler bug,
please contact the libFuzzer developers.
Also check https://bugs.llvm.org/show_bug.cgi?id=34636
for possible workarounds (tl;dr: don't use the old GNU ld)
{code}

There's a long thread about it here https://groups.google.com/forum/#!topic/llvm-dev/fnDXbyduLjw

and https://github.com/google/oss-fuzz/issues/1042

> [C++] Fuzzer builds fail out of the box on Ubuntu 16.04 using LLVM apt repos
> ----------------------------------------------------------------------------
>
>                 Key: ARROW-2256
>                 URL: https://issues.apache.org/jira/browse/ARROW-2256
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: C++
>            Reporter: Wes McKinney
>            Priority: Major
>             Fix For: 0.14.0
>
>
> I did a clean upgrade to 16.04 on one of my machine and ran into the problem described here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866087
> I think this can be resolved temporarily by symlinking the static library, but we should document the problem so other devs know what to do when it happens



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)