On Sat, Mar 7, 2020 at 3:36 PM Ludovic Courtès <ludo@gnu.org> wrote:

Hi,

Marnen Laibow-Koser <marnen@marnen.org> skribis:

> On Sat, Mar 7, 2020 at 10:12 AM Ludovic Courtès <ludo@gnu.org> wrote:

[...]

>> Could you provide a backtrace of the segfault?
>>
>
> I’m not sure how I would be able to get any more detailed debugging info
> than the logs that I posted in the GitLab issue. Have you looked at
> those? Alternatively, is there an environment variable or anything that
> would get Guile to provide more information when it does segfault?

I would just run GDB on the dumped core, and run “bt” there (apologies
if that info is already in the GitLab issue, I didn’t see it.)

There’s now an lldb backtrace at

https://gitlab.com/marnen/lilypond-mac-builder/issues/16#note_317315811 . Hopefully it’s somewhat useful?

Note that this is from a second affected user, who said that the issue went away for him after he reinstalled macOS (Catalina, FWIW).

Best,