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

ASF GitHub Bot commented on PROTON-1412:
----------------------------------------

Github user jdanekrh commented on the issue:

    https://github.com/apache/qpid-proton/pull/95
  
    I've done the cleanup.
    
    One thing I came across is that I was not able to easily build the fuzzers 
with a simple driver on Windows, because MSVC does not have weak linking. Since 
both afl-fuzz and libFuzzer do not work on Linux anyway, I think it is OK to 
disable this with MSVC.
    
    If I enable building and running the fuzzers with the simple driver, then 
Windows build is unchanged and Linux build shows results of the tests. The 
reason it is passing in Travis and not for me locally is that Travis does not 
enable sanitizers like `-fsanitize=address`.
    
    CI builds with fuzzer enabled:
    
    https://ci.appveyor.com/project/ke4qqq/qpid-proton/build/master.1117
    https://travis-ci.org/apache/qpid-proton/builds/205374841


> Add fuzzers to proton-c tests
> -----------------------------
>
>                 Key: PROTON-1412
>                 URL: https://issues.apache.org/jira/browse/PROTON-1412
>             Project: Qpid Proton
>          Issue Type: Wish
>          Components: proton-c
>            Reporter: Jiri Danek
>            Priority: Minor
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Add fuzzers to proton-c test suite in order to be able to perform fuzz 
> testing of qpid-proton.
> This would then allow including qpid-proton to 
> https://github.com/google/oss-fuzz, a service that executes fuzzers for 
> opensource projects.
> I intend to propose a patch to do this today or tomorrow by cleaning up my 
> proof-of-concept 
> https://github.com/jdanekrh/qpid-proton-fuzz/tree/master/proton-c/src/tests.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to