Re: [cfe-users] Syncing up clang and clang-tools-extra with llvm for git

[Adrian Prantl via cfe-users]

The --update option is meant to be used to rebuild the accelerator tables in an 
existing .dSYM. Can you share the crash log for when dsymutil fails?

-- adrian

> On Mar 12, 2018, at 8:16 AM, David Blaikie  wrote:
> 
> +Adrian for questions about dsymutil.
> 
> Though I'm not quite sure how the subject line relates to the question?
> 
> On Thu, Mar 8, 2018 at 7:03 PM Michael Eisel via cfe-users 
> mailto:cfe-users@lists.llvm.org>> wrote:
> Hi,
> 
> I'm hitting some segfault when I run dsymutil without any flags, but when I 
> add "-update", it works. I'm curious about this flag, but i can't find any 
> documentation. When it "updates", does that mean it needs an existing dSYM 
> file to begin with? And what are the actual pros and cons of using this flag? 
> FYI I'm trying to generate a dSYM for crash symbolication for an iOS app.
> 
> Thanks,
> Michael
> ___
> cfe-users mailing list
> cfe-users@lists.llvm.org 
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users 
> 

___
cfe-users mailing list
cfe-users@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users

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

[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 using the dSYMs, but 
> Xcode is?

I'm not familiar with the crash reporters you mentioned, but what Duncan said 
is accurate. Xcode, lldb, and atos will use the inlining debug information 
stored in the debug info (the dSYM) to also show the inlined stack frames. The 
tools you were using probably don't.

-- adrian

> 
> Any ideas Adrian?
> 
>> On Mar 30, 2018, at 16:28, Michael Eisel via cfe-users 
>>  wrote:
>> 
>> 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 PLCrashReporter and Crashlytics, I 
>> don't see f1 or f3 in the stack trace, implying that inline functions aren't 
>> included. However, when I cause the crash in the Xcode debugger, I see the 
>> inline functions in the stack trace. Is there additional context that Xcode 
>> would have, e.g. with symbols in the binary, that the crash reporters with 
>> their dSYM files don't?
>> 
>> Thanks,
>> Michael
>> ___
>> cfe-users mailing list
>> cfe-users@lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users
> 

___
cfe-users mailing list
cfe-users@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users