Teach LLDB to understand INLINE and INLINE_ORIGIN records in breakpad.
They have the following formats:
INLINE inline_nest_level call_site_line call_site_file_num origin_num [address size]+ INLINE_ORIGIN origin_num name
INLNIE_ORIGIN is simply a string pool for INLINE so that we won't have
duplicated names for inlined functions and can show up anywhere in the symbol
file.
INLINE follows immediately after FUNC represents the ranges of momery
address that has functions inlined inside the function.
In lldb, we treat (or at least try to) debug info as "user input", meaning invalid/inconsistent debug info should not crash the debugger. While the situation is not as critical for breakpad as it is for dwarf (due to it not having as many producers), I think the principle remains.
It doesn't really matter much how you handle invalid records (like, it'd be fine if you just throw away all inline info for the affected function), but it'd be nice if it does not crash lldb.