It's become sort of a weird vermiform day.
I finally have an executable running on the embedded platform, and in demo mode it works exactly like expected. However, in real mode-- well, it crashes hard. Segmentation fault.
At this point, it's firmly to be expected that it wouldn't work, and it wouldn't work in such a way that I can get no clues from its operation whatsoever.
I could add some lines to the code to write debug messages to the console. But if I do that, I will have to recompile, which will take several hours, by which time I hope to be on teh road going home.
I should be able to open the debug log file, but when it crashes so hard, the log file appears to be unavailable.
Ah, well, suck is life.
I finally have an executable running on the embedded platform, and in demo mode it works exactly like expected. However, in real mode-- well, it crashes hard. Segmentation fault.
At this point, it's firmly to be expected that it wouldn't work, and it wouldn't work in such a way that I can get no clues from its operation whatsoever.
I could add some lines to the code to write debug messages to the console. But if I do that, I will have to recompile, which will take several hours, by which time I hope to be on teh road going home.
I should be able to open the debug log file, but when it crashes so hard, the log file appears to be unavailable.
Ah, well, suck is life.
- Current Mood:
apathetic
Profile
magicmarmot- Tom Ramcigam
- Magic Marmot Studios
Comments
I've spent my share of time with a logic probe checking for pins toggling to find out if my code was even running.
I know the majority of the code works, so it's down to the link layer, invoking the drivers. Which means it's not my coding issue. Which also means it will be a premiere bitch to find-- kernel-level debugging is a real easy way to lose your hair.