?

Log in

No account? Create an account

Previous Entry | Next Entry

Feel my disease.

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.

Comments

( 2 comments — Leave a comment )
stark0228
Aug. 8th, 2003 01:34 pm (UTC)
Output has always been a pain in the ass on my embedded projects. Nothing like turning a device on and getting no output. Is my code bad? Are the compiler settings wrong? Is there a problem with the hardware (which unlike you, I didn't know how to fix).

I've spent my share of time with a logic probe checking for pins toggling to find out if my code was even running.
magicmarmot
Aug. 8th, 2003 02:23 pm (UTC)
As have I, but this one's in a sealed box. It's linux, which helps, and it's a frankenstein creation of drivers, data files, cables, kludges, and it's just way too much to expect it all works.

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.
( 2 comments — Leave a comment )

Latest Month

April 2012
S M T W T F S
1234567
891011121314
15161718192021
22232425262728
2930     

Tags

Page Summary

Powered by LiveJournal.com
Designed by Tiffany Chow