On Oct 4, 2012, at 10:12 AM, Jerry Krinock wrote:
> If I create such an error on my Mac, where backtrace() has the benefit of
> either an unstripped Debug build or a matching dSYM file, the backtrace is
> symbolized correctly.
If you have the matching dSYM file for your users' bug reports, you
On 2012 Oct 04, at 11:07, Fritz Anderson wrote:
> If symbols are not present in the executable, the trace will search backwards
> in memory to the closest symbol that happens to be defined.
Thank you, Fritz. It seems like the backtracer should have a way to avoid
presenting incorrect informa
On 4 Oct 2012, at 12:12 PM, Jerry Krinock wrote:
> 1 MyFramework 0x00105066 MyInlineFunction + 188607
...
> If I create such an error on my Mac, where backtrace() has the benefit of
> either an unstripped Debug build or a matching dSYM file, the backtrace is
> symbolized correctly.
...
> Wha