Re: [cfe-users] Crash reporting for inline functions

2018-03-30 Thread Adrian Prantl via cfe-users
> On Mar 30, 2018, at 4:34 PM, Duncan P. N. Exon Smith > wrote: > > +Adrian > > I suspect the crash reporters are giving you results based solely on the > symbol table. The dSYM has extra information from the debug info so it can > fill in the gaps. Perhaps the crash reporters aren't usin

Re: [cfe-users] Crash reporting for inline functions

2018-03-30 Thread Duncan P. N. Exon Smith via cfe-users
+Adrian I suspect the crash reporters are giving you results based solely on the symbol table. The dSYM has extra information from the debug info so it can fill in the gaps. Perhaps the crash reporters aren't using the dSYMs, but Xcode is? Any ideas Adrian? > On Mar 30, 2018, at 16:28, Micha

[cfe-users] Crash reporting for inline functions

2018-03-30 Thread Michael Eisel via cfe-users
Hi, I've been playing around with a stack trace of inlined functions, e.g.: void __attribute__((always_inline)) f1() { f2(); } void __attribute__((noinline)) f2() { f3(); } void __attribute__((always_inline)) f3() { abort(); } When I use various crash reporters, like PLCrashReporte