K2
I did the PR for oss-fuzz on an initial test case, I do think we should be working on the bugs from these various API as we see from issue...
@lemire I mentioned you in https://github.com/google/oss-fuzz/pull/7144 for approval to integrate into oss-fuzz with the minimal fuzzer we went over a few weeks ago.
What would make a sensible test case if were to enroll into oss-fuz then?
Then perhaps to minimize the testroaring_bitmap_portable_deserialize_safe for now and update the test case in the future as we add more validation?
@lemire I just wrote a C++/CLI wrapper that allow's .NET callers (C#, F# etc..) to use the 64 bit CPP interface. It's able to be amalgamated since I used inline...
Sure I can take a look at CMake if you'd like or if you have other suggestions I'm open to it, maybe another .NET (the RogueException/CRoaring.Net is very good with...
Yes I will clean up and drop the Capstone one into a new repro. Thanks for the keystone link. I had not seen that one when I started, I like...
@aquynh I moved the Capstone.cs I was using into it's own repository [Capstone.NET](https://www.github.com/K2/Capstone.NET) So this is a 64 bit version specifically, people can use the other one for 32 still...
Here's the Linux / Windows portable version for .NET x64 https://github.com/K2/CapstoneCore I'll keep porting more arch as well.
Thanks! I'll take a look. BTW. The coreclr version is also available. I'll take a look.