duksta.org :: Blagh
Nokia e71 Bug Report - Phonebook match fail
Dear Nokia:
I filed this report via the 'email support' page on your website. Hopefully you'll fix this. I can, of course, work around it with judicious data entry sanitization, but I shouldn't have to.
Bug Report: Phone book match fails for incoming calls and SMS messages if phone book entry contains dashes Version Info: 300.21.012 18-06-2009 RM-346 Nokia E71-1 (27) Details: When a phone book phone number entry contains dashes (and possibly when it starts with a +), the calling (or texting) party name from the phone book is not matched properly. It seems that there's a regex failure. Steps to reproduce: Enter phone book entry in the form +1-NPA-NXX-NNNN. Receive call and text from that number. Observe that the entry is not matched properly. Desired Behavior: The lookup algorithm should strip out the dashes before matching to the phone book entries. Other Notes: This worked properly on my E61i. You might want to check that code tree to see what changed between releases.
Posted by John on September 5, 2009
Breadboard Template

In preparation for the Arduino Class I'm teaching this month at AS220 Labs, I made this breadboard template in Inkscape to make it easier to layout circuits for the presentations.
I figure this will be useful to others, so you can grab the SVG here. Enjoy!
Posted by John on June 13, 2009
Building Statically Linked Binaries with make on Linux/Unix
Posting this mostly as a reminder to myself for the next time I have to do this.
For those who don't know, a statically linked binary is an executable that does not require any support libraries. All the required support libraries get included in the binary itself. This results in a binary that will run on any system of the right CPU type (i386, x86_64, ppc, etc.) The downside of this is that the resulting binary is going to be quite large. If you're doing forensics on a system, it's always handy to have a set of system utilities (ls, ps, sh, chown, chmod, netstat, vi, cp, rm, mkdir, rmdir, etc) that you have built yourself as statically linked binaries so you can trust them in case a system is root kitted.
Normally, when you download a tarball of source code, you'll do the standard "configure; make; make install" to build it. If you want a statically linked binary, replace the plain "make" with:
make SHARED=0 CC='gcc -static'
Posted by John on June 10, 2009
Archives