Breakpad generates short stack trace on ios

What steps will reproduce the problem?
1. Force application to crash.
2. dump_syms -a i386 -g AppName.app.dSYM AppName (i mean this unix executable 
file in /Objects-normal/i386) > AppName\ i386.breakpad
3. crash_report -S PathToFolderWithResultOfStepTwo dmpFile > somename.log

What is the expected output? What do you see instead?
I expect stack trace like this (it's from Xcode):
#0  0x0209d952 in __pthread_kill ()
#1  0x02061167 in pthread_kill ()
#2  0x01dd09c9 in abort ()
#3  0x01d9b53b in __assert_rtn ()
#4  0x0000dcaa in -[CrashClass crash] at 
/Users/user/TestBreakpad/TestBreakpad/CrashClass.m:14
#5  0x00002d8e in -[ViewController makeCrash] at 
/Users/user/TestBreakpad/TestBreakpad/ViewController.m:40
#6  0x00002d0c in -[ViewController crashTouchDown:] at 
/Users/user/TestBreakpad/TestBreakpad/ViewController.m:35

but i get something like this:
Thread 0 (crashed)
 0 libsystem_kernel.dyl                     0x0209d952 __pthread_kill + 0xa
 1 libsystem_sim_c.dyli                     0x01dd09c8 abort + 0x7e

What version of the product are you using? On what operating system?
Operating system: Mac OSX
Application for iOS
Xcode 5.1.1

Please provide any additional information below.
Stack trace in file generated by google breakpad is quite short and contains no 
unnecessary information like name of function where app crashed, but maybe i'm 
doing it wrong.

Original issue reported on code.google.com by marcin.g...@gmail.com on 8 Sep 2014 at 12:24

davidbrs / google-breakpad

Breakpad generates short stack trace on ios #604