Elliot

Another potentially interesting item to note is running sdcdb with -d=0xF I can see that the main function has no entry or exit. sdcdb: func 'main' has entry '0x0' exit '0x0' sdcdb: func '_main' has entry '0x0' exit '0x2f' sdcdb: function '_main' has the following C exePoints sdcdb: and the following ASM exePoints simi: openSimulator I'm wondering if the problem is actually symbol generation. I know sdcdb is experimental but is nobody else using it?

SDCDB SegFault on 4.1.0