Eric Kilmer

Hello! Adding to this issue: I've added support for Ghidra's C++ sleigh project to [Mishegos](https://github.com/trailofbits/mishegos), a differential fuzzer for x86_64 decoders. More info about Mishegos can be found in this...

Looks like the mac runner died while building LLVM https://dev.azure.com/vcpkg/public/_build/results?buildId=76307&view=logs&j=7b75bd19-17d3-53d4-00fd-23f1a49a8ba4&t=a23dba4e-3a62-59dc-a73c-a7222676d7a4&l=1001

Tests are failing because the spec files aren't being compiled/installed. There are some spec targets you can un-exclude from all to make sure they're built

Hmmm. It doesn't look like the additional patches are being applied, so maybe that's what is causing failures? ``` [ 44%] Performing patch step for 'ghidrasource-populate' Applying: Small improvements to...

Ah. Yeah I didn't see that it was originally a normal variable for the patches. Mixing and matching still doesn't make sense to me, so it's always good to match...

@dns43 I just realized now that the CLA hasn't been signed. Could you please sign that? It must be signed before merging this PR.

This might be helpful: A list of all challenges in the final event and the CWEs that the challenge-writers thought the POVs represented http://www.lungetech.com/cgc-corpus/cwe/cfe/ Each challenge page also provides a...

This would be nice to catch simple runtime issues like missing symbols, even if the workers seem to build correctly (relevant PR for bddisasm https://github.com/bitdefender/bddisasm/pull/53, but this could have easily...

The instruction bytes I've tested are the following. `S_SUCCESS` means Ghidra should correctly decode to the following disassembly text and `S_FAILURE` means Ghidra was correctly unable to disassemble the bytes....

I've also been looking into the `XACQUIRE` and `XRELEASE` prefixes, which are related to `LOCK`. They require new pcodeops and context register fields. I am working on that implementation, which...