From: Marnen Laibow-Koser <marnen@marnen.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Ivo Bouwmans <muziek@bouwmans.name>, 39863@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 [thread overview]
Message-ID: <CAKZYM4BLXhHbs7UEkkdVTOAsUW=e_8btNtWTLiyyM4Rk-3H07A@mail.gmail.com> (raw)
In-Reply-To: <87o8t7gawg.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
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,
--
Marnen Laibow-Koser marnen@marnen.org http://www.marnen.org Sent from Gmail
Mobile
[-- Attachment #2: Type: text/html, Size: 2025 bytes --]
next prev parent reply other threads:[~2020-04-03 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 20:30 bug#39863: Guile 1.8, apparent segfault on some Macs running Mojave Marnen Laibow-Koser
2020-03-07 15:12 ` Ludovic Courtès
2020-03-07 15:38 ` Marnen Laibow-Koser
2020-03-07 20:36 ` Ludovic Courtès
2020-03-07 21:27 ` Marnen Laibow-Koser
2020-04-03 17:02 ` Marnen Laibow-Koser [this message]
2020-04-05 13:29 ` Ludovic Courtès
2020-04-05 21:46 ` Marnen Laibow-Koser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKZYM4BLXhHbs7UEkkdVTOAsUW=e_8btNtWTLiyyM4Rk-3H07A@mail.gmail.com' \
--to=marnen@marnen.org \
--cc=39863@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=muziek@bouwmans.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).