No, I don't. It just hangs with a blank screen. I haven't got the DC setup to run in the debugger in any case, but I would like to have a default exception handler that let me know when it blew up and why. Getting an unaligned memory access fault vs divide by zero makes tracking problems easier.
Having gotten into the program with networking active, now I ran into a weirder bug - this line gives an empty string.
Code: Select all
sprintf(dc_net_ipaddr, "%u.%u.%u.%u", netdev->ip_addr[0], netdev->ip_addr[1], netdev->ip_addr[2], netdev->ip_addr[3]);
Yes, the char array dc_net_ipaddr is big enough. It's not being overwritten by anything either. I've never seen sprintf fail like that.
It originally used %d instead of %u, but I changed them to see if it made a difference... it didn't.
EDIT: Found that problem - when I was editing this for the DC (this is a DC port of a PSP port of an AROS port of my AmigaPPC port of ADoom), I somehow lost one level of indirection on the ipaddr string. My GUI uses pointers to pointers to strings. I'm a little surprised it didn't just crash like the last bug.