Enkelmann

> Hmm, if I understand correctly, there is no way actually to cause this at this time. At least I hope so. But there is already an [accepted RFC](https://rust-lang.github.io/rfcs/2116-alloc-me-maybe.html) for...

I need more context to help you. ;-) For example, what kind of binary are you trying to analyze? I am aware that this error gets generated if you try...

If your `crackme0x01` binary is not from an exotic architecture with address lengths greater than 64 bits then this is a bug in the cwe_checker. Why this only fails for...

Thanks for sharing the example binary! As a quick update: I found the root cause of the bug and I am currently working on a fix. The fix should be...

The fix is now merged (see PR #353). And I confirmed that the cwe_checker does not crash anymore when analyzing your example binary.

Whether the binary is stripped or not should not make a difference for the check. This looks more like a bug in the cwe_checker. Can you provide a binary where...

This is probably related to the CPU type of the chip. Can you tell me what value is contained in the `processor_id` field of the `ATxmega64B3.json` configuration file? I could...

I have not found a sample for this processor type in my sources yet. When using this processor ID on other binaries I get a different error than what you...

The vendor website seems to provide enough resources for compiling simple example binaries for the architecture. I will try that. But it might take some days until I find the...

OK, I managed to fix your initial issue and some other issues on top of that in #286. However, analyzing an AVR8 sample still leads to panics that now should...