From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Marnen Laibow-Koser Newsgroups: gmane.lisp.guile.bugs Subject: bug#39863: Guile 1.8, apparent segfault on some Macs running Mojave Date: Sat, 7 Mar 2020 10:38:11 -0500 Message-ID: References: <875zfgjj24.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000060fdb405a0458f76" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="76757"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Ivo Bouwmans , 39863@debbugs.gnu.org To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Original-X-From: bug-guile-bounces+guile-bugs=m.gmane-mx.org@gnu.org Sat Mar 07 18:10:17 2020 Return-path: Envelope-to: guile-bugs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jAcxs-000JoI-OL for guile-bugs@m.gmane-mx.org; Sat, 07 Mar 2020 18:10:16 +0100 Original-Received: from localhost ([::1]:50944 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jAcxr-0004Kk-Qj for guile-bugs@m.gmane-mx.org; Sat, 07 Mar 2020 12:10:15 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50112) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jAcxh-0004Ha-1L for bug-guile@gnu.org; Sat, 07 Mar 2020 12:10:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jAcxe-0005xU-FV for bug-guile@gnu.org; Sat, 07 Mar 2020 12:10:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:41508) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jAcxe-0005wy-63 for bug-guile@gnu.org; Sat, 07 Mar 2020 12:10:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jAcxe-0001nc-1K for bug-guile@gnu.org; Sat, 07 Mar 2020 12:10:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Marnen Laibow-Koser Original-Sender: "Debbugs-submit" Resent-CC: bug-guile@gnu.org Resent-Date: Sat, 07 Mar 2020 17:10:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 39863 X-GNU-PR-Package: guile Original-Received: via spool by 39863-submit@debbugs.gnu.org id=B39863.15836009876883 (code B ref 39863); Sat, 07 Mar 2020 17:10:01 +0000 Original-Received: (at 39863) by debbugs.gnu.org; 7 Mar 2020 17:09:47 +0000 Original-Received: from localhost ([127.0.0.1]:47479 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jAcxN-0001mw-VY for submit@debbugs.gnu.org; Sat, 07 Mar 2020 12:09:47 -0500 Original-Received: from mail-yw1-f44.google.com ([209.85.161.44]:45393) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jAbX2-000860-0Y for 39863@debbugs.gnu.org; Sat, 07 Mar 2020 10:38:28 -0500 Original-Received: by mail-yw1-f44.google.com with SMTP id d206so5360346ywa.12 for <39863@debbugs.gnu.org>; Sat, 07 Mar 2020 07:38:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marnen-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=d6gBj/lIQPEBNm8n3mlm+ABuoodnJqdI8oef5g95VU0=; b=YHhCgKZzWqf8+BqcmFFOVoLdaogGiat2/c7rgeri7wvNVTWvj/qs73V3yMPmtvQz7B f7mTZHqRmnzfKFEnlf7ybzpcrlqNlkYw0NaacMRYByB1VdqMhZkrmsWQCmWIx1AmdVSc 99GEZ7c6kdfkaN/lQMsfmTbwlIae9muo8u1I9AxWLB1uzVW5SolW4v0GQydnhnvlAQc3 M/ZROSss3YhWybWk3/vL8InJ3voEImSBs3YRYhXW0O3ynGhwCIQPHTDFuJyaIt0t09HQ bqoOZmogWnQJXOYNGec4cjdlU1e8elbqke0BP822SevT+QKiW2BwAQWZG39mMgQvKukj y54Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=d6gBj/lIQPEBNm8n3mlm+ABuoodnJqdI8oef5g95VU0=; b=nF5sNwIBgHKyfMqgyfIzLlhWGJOgRZchBTcIdo75wZgEM9hH87jlLC+gFSNRjLXIY/ IXtbVddvS10S5HtRVY6GQR7hloSLIgzzlMJLawauXCA81aff9oh+eejGyWRIfxp3jL5m vefFuUATtz1wGvcW7b2DpHqVbeannxPJElpydaypZ3aM7qE3sDOigpk5xoi9aIG325Mh X3Xw5D5ea5SHwkFhuyUKsCLgbuNJ+Cf3VQNgA/pBOQIkLrj++0aa/Q1Np9PI22e4LkZv 4Tt+DTtjYUR9vlcSSifFlI5257vjL5gf4SZuS9qHN77+f36mncdZyG73b3hyF7AX3Ums x5xw== X-Gm-Message-State: ANhLgQ06hK4V/xnYhPqetZjFD+NEy8Hphjnh7FWiFUH9P9cPgxzk/2CP omDxDPQZuY2PxEWFWVZdpVVeEs/UnESzUfmxundUqQ== X-Google-Smtp-Source: ADFU+vvic5xlge+nuJ9F7h1n6q+2P1ThZEMCuJOyAKUrw1XR1YWX1PluR8EeX5P5TqYfbRmHx81rLDupnqhK4TAXUD4= X-Received: by 2002:a25:2554:: with SMTP id l81mr9041912ybl.375.1583595502232; Sat, 07 Mar 2020 07:38:22 -0800 (PST) In-Reply-To: <875zfgjj24.fsf@gnu.org> X-Mailman-Approved-At: Sat, 07 Mar 2020 12:09:44 -0500 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-guile@gnu.org List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guile-bounces+guile-bugs=m.gmane-mx.org@gnu.org Original-Sender: "bug-guile" Xref: news.gmane.io gmane.lisp.guile.bugs:9624 Archived-At: --00000000000060fdb405a0458f76 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Mar 7, 2020 at 10:12 AM Ludovic Court=C3=A8s wrote: > Hi, > > Marnen Laibow-Koser skribis: > > > I'm not sure this is a bug report yet, but it may become one. I'm havi= ng > > 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 include= s > > 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 righ= t > > 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? > I=E2=80=99m 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? > Does the problem occur on GNU/Linux as well? > I have no way of knowing. I discovered this issue in the course of figuring out how to package LilyPond into a 64-bit Mac .app bundle. I=E2= =80=99ve never run this particular build process on Linux, and I=E2=80=99m not sure = that it would even be meaningful to do so given that the primary point of it is to make a Mac .app. > Is it a recent regression of your LilyPond package for macOS? I=E2=80=99m afraid that question doesn=E2=80=99t have much meaning either: = this packaging is newly developed, so there=E2=80=99s nothing to regress *from*. What I c= an tell you is that it consistently affects one user (and, I believe, on all builds I=E2=80=99ve so far done with this method), but everyone else has no proble= ms with these builds, and the user who *is* having problems was able to run the 32-bit Mac builds, but those are built by a somewhat different process. I know this information is less helpful and comprehensive than we might like, but since I=E2=80=99m still developing this particular build and pack= aging process, there=E2=80=99s very little to go on. > > 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=E2=80=99t make any promises. Understood. Believe me, if I could upgrade to a recent Guile, I would, but my objective here is mostly to get a working 64-bit Mac build of LilyPond while changing the code as little as possible. :) > > Thanks, > Ludo=E2=80=99. > --=20 Marnen Laibow-Koser marnen@marnen.org http://www.marnen.org Sent from Gmail Mobile --00000000000060fdb405a0458f76 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


<= div>
On Sat, Mar 7, 2020 at 10:12 AM L= udovic Court=C3=A8s <l= udo@gnu.org> wrote:
Hi,

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

> I'm not sure this is a bug report yet, but it may become one.=C2= =A0 I'm having
> what looks like a Guile segfault issue for some Mac OS Mojave (10.14)<= br> > users. I've been packaging 64-bit Mac builds of LilyPond, which in= cludes
> 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 righ= t
> 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 is= sue, so I
> thought I'd come over here...
>
> There's more information in the GitLab issue I mentioned above, bu= t please
> let me know what else would be helpful in diagnosing and fixing this > particular problem.=C2=A0 (Upgrading to a recent Guile is not an optio= n 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?

I=E2= =80=99m not sure how I would be able to get any more detailed debugging inf= o than the logs that I posted in the GitLab issue.=C2=A0 Have you looked at= those?=C2=A0 Alternatively, is there an environment variable or anything t= hat would get Guile to provide more information when it does segfault?


Does the problem occur on GNU/Linux as well?

I hav= e no way of knowing.=C2=A0 I discovered this issue in the course of figurin= g out how to package LilyPond into a 64-bit Mac .app bundle.=C2=A0 I=E2=80= =99ve never run this particular build process on Linux, and I=E2=80=99m not= sure that it would even be meaningful to do so given that the primary poin= t of it is to make a Mac .app.=C2=A0


Is it a recent regression of your LilyPond package for macOS?
<= div dir=3D"auto">
I=E2=80=99m afraid that questi= on doesn=E2=80=99t have much meaning either: this packaging is newly develo= ped, so there=E2=80=99s nothing to regress *from*.=C2=A0 What I can tell yo= u is that it consistently affects one user (and, I believe, on all builds I= =E2=80=99ve so far done with this method), but everyone else has no problem= s with these builds, and the user who *is* having problems was able to run = the 32-bit Mac builds, but those are built by a somewhat different process.= =C2=A0

I know this infor= mation is less helpful and comprehensive than we might like, but since I=E2= =80=99m still developing this particular build and packaging process, there= =E2=80=99s very little to go on.=C2=A0



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=E2=80=99t make any promises.

Understood.=C2=A0 Believe me, if I could upgrade to a recen= t Guile, I would, but my objective here is mostly to get a working 64-bit M= ac build of LilyPond while changing the code as little as possible. :)



Thanks,
Ludo=E2=80=99.
--
Marnen Laibow-Koser marnen@marnen.org http://www.marnen.org Sent from Gmail Mobile
--00000000000060fdb405a0458f76--