bug#30364: 26.0.91; thread crash on macos

[Eli Zaretskii]

> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Sat, 17 Feb 2018 20:54:54 -0800
> Cc: Noam Postavsky <npostavs@gmail.com>, 30364@debbugs.gnu.org, 
>       Noam Postavsky <npostavs@users.sourceforge.net>, Alan Third 
> <alan@idiocy.org>
> 
> On Sat, Feb 17, 2018 at 8:51 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > A Lisp backtrace from the crashing thread would be nice.  Also, the
> > C-level backtrace from that thread seems truncated, so it would be
> > good to see all of it.
> 
> Pardon my inexperience, but are there instructions on how to get these
> somewhere?

I don't use LLDB, so I can be of limited help here.

For the second issue, I'm guessing that there's some limitation on
the number of call-stack frames LLDB shows by default, so a way to
show more would be to increase that limit.

For the first issue, you will have to evaluate expressions manually,
unfortunately, as LLDB doesn't support canned command sequences that
we define in src/.gdbinit for GDB.  You will find some starting point
here:

  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30320#44
  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30320#47
  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30320#50

Thanks.