unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Marnen Laibow-Koser <marnen@marnen.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: Sat, 07 Mar 2020 16:12:03 +0100	[thread overview]
Message-ID: <875zfgjj24.fsf@gnu.org> (raw)
In-Reply-To: <CAKZYM4AM5VaZK3PYKRsV7sA0evpEo5kPvaZKCVeS+tGAS8Y0Bg@mail.gmail.com> (Marnen Laibow-Koser's message of "Sun, 1 Mar 2020 15:30:20 -0500")

Hi,

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

> I'm not sure this is a bug report yet, but it may become one.  I'm having
> what looks like a Guile segfault issue for some Mac OS Mojave (10.14)
> users. I've been packaging 64-bit Mac builds of LilyPond, which includes
> libguile 1.8. The builds work well for myself and for nearly everyone else,
> but one user (on Mojave, as am I) consistently reports a segfault right
> around the time libguile is loaded; see
> https://gitlab.com/marnen/lilypond-mac-builder/issues/16 . The LilyPond
> group hasn't provided much help on figuring out this particular issue, so I
> thought I'd come over here...
>
> There's more information in the GitLab issue I mentioned above, but please
> let me know what else would be helpful in diagnosing and fixing this
> particular problem.  (Upgrading to a recent Guile is not an option right
> now AFAIK: LilyPond barely works with Guile 2, let alone 3, and fixing
> *that* would probably be a much larger issue.)

Could you provide a backtrace of the segfault?

Does the problem occur on GNU/Linux as well?

Is it a recent regression of your LilyPond package for macOS?

Unfortunately, Guile 1.8 has been unmaintained for several years and its
code base has almost nothing in common with that of 2.0 and later, so I
won’t make any promises.

Thanks,
Ludo’.





  reply	other threads:[~2020-03-07 15:12 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 [this message]
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
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=875zfgjj24.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39863@debbugs.gnu.org \
    --cc=marnen@marnen.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).