If you're like me and always have issues with the "easy" processes of symbolicating a crash log (drag it to Organizer... as if), you can still brute force the symbolication process to get to the relevant stack traces. First, this does require that you at least have the exact binary version of the app the crash occurred under (but you don't need the dSYM). If you aren't sure which version of the app the crash log came from, you can compare the UUID mentioned in the crash log to the UUID of any relevant binaries you might have saved locally. You can find the UUID of your local app build by running...
dwarfdump -u /path/to/MyApp.app/MyApp
You can start by attempting to symbolicate the crash log with symbolicatecrash. This will often at least fill in the system calls for you. You can leave off the dSYM parameter you might otherwise have used.
Just for posterity, in case you do have the dSYM, you can use it as such:
symbolicatecrash /path/to/MyApp_2012-10-01_Device.crash /path/to/MyApp.app.dSYM
If that works, you're lucky, and don't need to worry about the rest of this post.
Setting up the nice convenience method I used above:
To find symbolicatecrash, should it differ from my alias above:
find /Applications/Xcode.app -name symbolicatecrash -type f
And, in case you get an error that DEVELOPER_DIR can't be found:
Next, use atos to symbolicate each memory address individually. Pull the memory address from the actual text of the crash log. Make sure to use the correct architecture version for the device now that we have armv7s to pay attention to as well.
atos -arch armv7 -o /path/to/MyApp.app/MyApp 0x0003b508
Repeat this for every method you want to symbolicate. It's time consuming, but if you are left with no other choices, this will at least unravel the mystery for you.
I suspect these tools will require that you've installed the command line tools through Xcode manually since they're no longer included in the base download. However, I've never actually tried running them without having done that install first, so I can't say for sure.
Anyway, I hope this helps out when you're in the tough bind of not having the original dSYM, or if your crash log is just failing to symbolicate correctly for any other annoying reason.