CodeWalker should create a "CodeWalkerFiles" folder in your home directory, with a file named "LastFile.txt" inside that. That's basically a black box for the parser.
Open that, and it should tell you what file was being parsed when it ran off into the weeds.
Currently there's an issue with pre-processor directives. Frankly, CodeWalker's parsers did not do a great job of handling those. We are addressing this in this next update.
That said, if CodeWalker does crash, please look for that folder, and that file, and see what it says. If it's a file you don't mind us seeing, please send us a copy!
Chilton@GetCodeWalker.com is where you can send it. And we're going to see if we can just perform some elegant back-out maneuver if it does fail to parse properly, in this next version.
I'm including a photo of the Android plugins folder in Unreal Engine 5. This next version of CodeWalker was able to parse all of the entire UE5 source code, but it took awhile. If I ever get a few free hours, I might let it run to completion on that, to see what all of the source looks like together.
We're hoping to get this update out soon, which includes the corrected binaries for Linux and MacOS.