Open chinatsu opened 8 years ago
Actually, scratch the "upon found tripcode" thing. I just attempted running it with the large sample target, in which mty_cl did find one and then ran for a bit longer. I assume there's something else that always triggers it.
It seems like MTY_CL crashes upon finding a matching tripcode, it doesn't always reach the point where it outputs the tripcode, but searching for a short target crashes the program almost immediately. In comparison, searching for an 8 char target makes the program run for a long time. I believe I have done the right things in regards to disabling DEP for mty_cl.exe, and my AMD driver is version 15.12. Do you have any ideas?
Here are some gdb logs, the current 0.52 release:
0.42 -g (from a closed issue which I was hoping is related to mine)