GNU bug report logs - #39863
Guile 1.8, apparent segfault on some Macs running Mojave

Previous Next

Full log

View this message in rfc822 format

From: Marnen Laibow-Koser <marnen <at> marnen.org>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: Ivo Bouwmans <muziek <at> bouwmans.name>, 39863 <at> debbugs.gnu.org
Subject: bug#39863: Guile 1.8, apparent segfault on some Macs running Mojave
Date: Fri, 3 Apr 2020 13:02:27 -0400

[Message part 1 (text/plain, inline)]

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

> Hi,
>
> Marnen Laibow-Koser <marnen <at> marnen.org> skribis:
>
> > On Sat, Mar 7, 2020 at 10:12 AM Ludovic Courtès <ludo <at> 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,
-- 
Marnen Laibow-Koser marnen <at> marnen.org http://www.marnen.org Sent from Gmail
Mobile

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.