Well, that was the reason why I asked for someone familiar with Cygwin's GDB; it's not really text based, it's more visual. But it has an option to get a gdb console, all old-school like.
And as for that backtrace, this is what it leads me to. (gdb) bt #0 0x00491a2f in probe () #1 0xffffffff in ?? () #2 0x00456760 in do_function (ch=0xd01574, do_fun=0x46dae0 <do_skills>, argument=0x43046e "") at interp.c:537 #3 0x00432815 in nanny (d=0xcff71c, argument=0xcffb39 "y") at comm.c:2062 #4 0x0042f290 in game_loop_unix (control=4) at comm.c:766 #5 0x0042ec98 in main (argc=1, argv=0xaa1008) at comm.c:396 #6 0x61005a9e in _libkernel32_a_iname () #7 0x61005d28 in _libkernel32_a_iname () #8 0x00491a9e in cygwin_crt0 () #9 0x0040103c in mainCRTStartup () #10 0xbff8b560 in _libkernel32_a_iname () #11 0xbff8b412 in _libkernel32_a_iname () #12 0xbff89dd5 in _libkernel32_a_iname () #13 0x23038a3d in ?? () Error: Cannot access memory at address 0xd0a2a24
