One thing that's coming in 2.1 is those values in crashlog.txt are going to be accurate again. Right now they're getting overwritten before we have a chance to write them out to disk. 
Once that's in place you should be able to use the firmware_symbolizer.py script in the SDK to find out where the crash was, if it was in your game code. I'll file a feature request to have that query symbols.db instead if the crash location is in the firmware.