3 ms·
When printf debugging is a luxury (2010)
- thetmkay 12y agoI once had a university project where we were implementing low-level threading for a custom OS, and had some task manipulating the signal handlers. Needless to say, we ran in to a few issues with the code we wrote. At that time, I was pretty much a print-line debugger (still mostly am). I failed that assignment, but in the process learned how to use gdb. I still do wish I had seen this post back* then though, just for the marks. *Disc: I'm not knowledgeable enough to know 100% this would have helped
- mmastrac 12y agoPrinting a string is luxury! When I was working on a Linux port to the Treo 650 ages ago, I had a single bit of output: an LED that I could turn on or off at certain parts of the boot sequence. That was good enough to get me to the point where the LCD could be initialized and I could do proper screen logging. I've done this for a handful of other projects as well. My first step is always locating a processor GPIO that controls something obvious (camera flash, status LED, etc) that I can use to figure out where I am in the boot process.
- crb3 12y agoOne bit/pin can be more than enough if you can code some state behind it. On one embedded MCU job, I ended up with just one port pin free. I tied it to a piezo-oscillator and played short Morse strings through it; that was my printf. (It helps that I'm a ham, so I could head-copy those messages.) Once I turned it over to production use, the techs found the difference in overall sound between "OK" and an error message useful enough that they kept it jumper-enabled. They did put tape over the oscillator's opening to cut down the amplitude, though.
- themodelplumber 12y ago"// If the camera flash fires five times in a row, the string was successfully changed"
- Sir_Cmpwn 12y agoI was once porting my OS to a new platform, and hadn't got the screen to work yet. What I did get to work was the screen's backlight, so I would have it blink to show debugging info. It was a huge pain in the ass.
- machrider 12y agoApparently simply panning around that blog (while zoomed in on mobile) is a luxury, because it seems to send you to different blog entries when you do it.
- JoshTheGeek 12y agoThe greatest "feature" of Blogspot. It is the most obnoxious thing on mobile devices.
- DanBC 12y agoNot as obnoxious as - on iOS - having my browser's focus stolen by an appstore link which switches me from browser to App Store. This is particularly bad when visiting Pinterest. So bad that I stopped visiting Pinterest at all because I hate the behaviour. It is so obviously broken that I'm surprised they still do it.
- JoshTheGeek 12y agoA game that is popular at my school has these modal ads with a close button that is smaller than you can accurately tap. Every third time it opens I end up in the App Store. It drives me nuts. A confirmation would be nice.
- niccl 12y agoLuxury. We used to _dream_ of printf debugging when we're doing embedded microcontroller systems! (at least the ones I work on). There the debugging is toggling a port pin and examining with an oscilloscope. I typically toggle it different numbers of times at different places in the code to see where I've got to.
- ctz 12y agoI love ARM semihosting for this reason. It's obviously insanely slow, but unlike a UART it doesn't need any extra hardware and the target is halted while the slow bit is taking place.
- sliverstorm 12y agoI grew fond of printing a char, after I spent some time snooping a uart. The o-scope in capture mode (I realize this wasn't always an option) grabs the char. Handy because I find char waveforms very easy to recognize at just a glance, and you don't have to measure periodicity or count toggles. Even if you don't have a uart, you can write a little proc to bit-bang a pin.
- ijager 12y agoWhen developing for microcontrollers and for example my leds aren't working, I like to define a place in memory where I write values to depending on the place in code. Then just read out that memory address with OpenOCD (jtag of swd). #define debugVar ((uint32_t *) 0x10007000) *debugVar = 1; *debugVar = 2; *debugVar = 0xdeadcafe;
- pantalaimon 12y agoI found tiny printf incredibly useful for this [1] http://www.sparetimelabs.com/tinyprintf/tinyprintf.php http://www.sparetimelabs.com/tinyprintf/tinyprintf.php [2] https://github.com/cjlano/tinyprintf https://github.com/cjlano/tinyprintf (32bit version)
- dkersten 12y agoI did this too. My life was a lot simpler on the projects where I could connect to UART and actually output text, but that wasn't always the case.
- Jare 12y agoMy first commercial 8-bit games (Sinclair Spectrum and Amstrad CPC) were developed entirely with border color as the only debugging tool. Figuring out a particular stack corruption bug was a miracle, and there was at least another bug that went unfixed (just changed the level map and it stopped happening). Those were the days ahem.
- beat 12y agoIf printf doesn't work, then just instantiate a Logger! </LetThemEatCake> There are some things I miss about doing hardcore embedded programming. This is not one of them.
- sliverstorm 12y agoDon't forget binary size. Often I find calling printf() links in a bunch of gunk- I'm not quite sure why- exploding binary size 10-20kB. This is, of course, mostly a problem on microcontrollers rather than PC's.
- justincormack 12y agoIt is a whole parser plus number parsing too. Few implementations compile at runtime if the pattern is known.