GNU logs - #39863, boring messages

Message sent to bug-guile@HIDDEN:

Subject: bug#39863: Guile 1.8, apparent segfault on some Macs running Mojave
Resent-From: Marnen Laibow-Koser <marnen@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guile@HIDDEN
Resent-Date: Sun, 01 Mar 2020 20:45:02 +0000
Resent-Message-ID: <handler.39863.B.158309547026381 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 39863 <at> debbugs.gnu.org
Cc: Ivo Bouwmans <muziek@HIDDEN>
MIME-Version: 1.0
From: Marnen Laibow-Koser <marnen@HIDDEN>
Date: Sun, 1 Mar 2020 15:30:20 -0500
Message-ID: <CAKZYM4AM5VaZK3PYKRsV7sA0evpEo5kPvaZKCVeS+tGAS8Y0Bg@HIDDEN>
Content-Type: multipart/alternative; boundary="0000000000001bbcc9059fd0f1ae"
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

--0000000000001bbcc9059fd0f1ae
Content-Type: text/plain; charset="UTF-8"

Hi there!

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.)

Best,
-- 
Marnen Laibow-Koser
marnen@HIDDEN
http://www.marnen.org

--0000000000001bbcc9059fd0f1ae
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi there!<div><br></div><div>I&#39;m not sure this is a bu=
g report yet, but it may become one.=C2=A0 I&#39;m having what looks like a=
 Guile segfault issue for some Mac OS Mojave (10.14) users. I&#39;ve been p=
ackaging 64-bit Mac builds of LilyPond, which includes libguile 1.8. The bu=
ilds work well for myself and for nearly everyone else, but one user (on Mo=
jave, as am I) consistently reports a segfault right around the time libgui=
le is loaded; see <a href=3D"https://gitlab.com/marnen/lilypond-mac-builder=
/issues/16">https://gitlab.com/marnen/lilypond-mac-builder/issues/16</a> . =
The LilyPond group hasn&#39;t provided much help on figuring out this parti=
cular issue, so I thought I&#39;d come over here...<br clear=3D"all"><div><=
br></div><div>There&#39;s more information in the GitLab issue I mentioned =
above, but please let me know what else would be=C2=A0helpful in diagnosing=
 and fixing this particular problem.=C2=A0 (Upgrading to a recent Guile is =
not an option right now AFAIK: LilyPond barely works with Guile 2, let alon=
e 3, and fixing *that* would probably be a much larger issue.)</div><div><b=
r></div><div>Best,</div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" d=
ata-smartmail=3D"gmail_signature">Marnen Laibow-Koser<br><a href=3D"mailto:=
marnen@HIDDEN" target=3D"_blank">marnen@HIDDEN</a><br><a href=3D"ht=
tp://www.marnen.org" target=3D"_blank">http://www.marnen.org</a></div></div=
></div>

--0000000000001bbcc9059fd0f1ae--

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Marnen Laibow-Koser <marnen@HIDDEN>
Subject: bug#39863: Acknowledgement (Guile 1.8, apparent segfault on some
 Macs running Mojave)
Message-ID: <handler.39863.B.158309547026381.ack <at> debbugs.gnu.org>
References: <CAKZYM4AM5VaZK3PYKRsV7sA0evpEo5kPvaZKCVeS+tGAS8Y0Bg@HIDDEN>
X-Gnu-PR-Message: ack 39863
X-Gnu-PR-Package: guile
Reply-To: 39863 <at> debbugs.gnu.org
Date: Sun, 01 Mar 2020 20:45:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-guile@HIDDEN

If you wish to submit further information on this problem, please
send it to 39863 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
39863: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D39863
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-guile@HIDDEN:

Subject: bug#39863: Guile 1.8, apparent segfault on some Macs running Mojave
Resent-From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guile@HIDDEN
Resent-Date: Sat, 07 Mar 2020 15:13:06 +0000
Resent-Message-ID: <handler.39863.B39863.158359393620780 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Marnen Laibow-Koser <marnen@HIDDEN>
Cc: Ivo Bouwmans <muziek@HIDDEN>, 39863 <at> debbugs.gnu.org
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
References: <CAKZYM4AM5VaZK3PYKRsV7sA0evpEo5kPvaZKCVeS+tGAS8Y0Bg@HIDDEN>
Date: Sat, 07 Mar 2020 16:12:03 +0100
In-Reply-To: <CAKZYM4AM5VaZK3PYKRsV7sA0evpEo5kPvaZKCVeS+tGAS8Y0Bg@HIDDEN>
 (Marnen Laibow-Koser's message of "Sun, 1 Mar 2020 15:30:20 -0500")
Message-ID: <875zfgjj24.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hi,

Marnen Laibow-Koser <marnen@HIDDEN> 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 els=
e,
> 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=E2=80=99t make any promises.

Thanks,
Ludo=E2=80=99.

Message sent to bug-guile@HIDDEN:

Subject: bug#39863: Guile 1.8, apparent segfault on some Macs running Mojave
Resent-From: Marnen Laibow-Koser <marnen@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guile@HIDDEN
Resent-Date: Sat, 07 Mar 2020 17:10:01 +0000
Resent-Message-ID: <handler.39863.B39863.15836009876883 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
Cc: Ivo Bouwmans <muziek@HIDDEN>, 39863 <at> debbugs.gnu.org
MIME-Version: 1.0
References: <CAKZYM4AM5VaZK3PYKRsV7sA0evpEo5kPvaZKCVeS+tGAS8Y0Bg@HIDDEN>
 <875zfgjj24.fsf@HIDDEN>
In-Reply-To: <875zfgjj24.fsf@HIDDEN>
From: Marnen Laibow-Koser <marnen@HIDDEN>
Date: Sat, 7 Mar 2020 10:38:11 -0500
Message-ID: <CAKZYM4BKJCOv2s5fG4KipS_BTw6u-dMFQ_FDHC0PQA2Go+bFjQ@HIDDEN>
Content-Type: multipart/alternative; boundary="00000000000060fdb405a0458f76"
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

--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 <ludo@HIDDEN> wrote:

> Hi,
>
> Marnen Laibow-Koser <marnen@HIDDEN> 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@HIDDEN http://www.marnen.org Sent from Gmail
Mobile

--00000000000060fdb405a0458f76
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><div><br></div><div><br><div class=3D"gmail_quote"></div></div></div><=
div><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Mar 7, 2020 at 10:12 AM L=
udovic Court=C3=A8s &lt;<a href=3D"mailto:ludo@HIDDEN" target=3D"_blank">l=
udo@HIDDEN</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;=
padding-left:1ex;border-left-color:rgb(204,204,204)">Hi,<br>
<br>
Marnen Laibow-Koser &lt;<a href=3D"mailto:marnen@HIDDEN" target=3D"_bla=
nk">marnen@HIDDEN</a>&gt; skribis:<br>
<br>
&gt; I&#39;m not sure this is a bug report yet, but it may become one.=C2=
=A0 I&#39;m having<br>
&gt; what looks like a Guile segfault issue for some Mac OS Mojave (10.14)<=
br>
&gt; users. I&#39;ve been packaging 64-bit Mac builds of LilyPond, which in=
cludes<br>
&gt; libguile 1.8. The builds work well for myself and for nearly everyone =
else,<br>
&gt; but one user (on Mojave, as am I) consistently reports a segfault righ=
t<br>
&gt; around the time libguile is loaded; see<br>
&gt; <a href=3D"https://gitlab.com/marnen/lilypond-mac-builder/issues/16" r=
el=3D"noreferrer" target=3D"_blank">https://gitlab.com/marnen/lilypond-mac-=
builder/issues/16</a> . The LilyPond<br>
&gt; group hasn&#39;t provided much help on figuring out this particular is=
sue, so I<br>
&gt; thought I&#39;d come over here...<br>
&gt;<br>
&gt; There&#39;s more information in the GitLab issue I mentioned above, bu=
t please<br>
&gt; let me know what else would be helpful in diagnosing and fixing this<b=
r>
&gt; particular problem.=C2=A0 (Upgrading to a recent Guile is not an optio=
n right<br>
&gt; now AFAIK: LilyPond barely works with Guile 2, let alone 3, and fixing=
<br>
&gt; *that* would probably be a much larger issue.)<br>
<br>
Could you provide a backtrace of the segfault?<br>
</blockquote><div dir=3D"auto"><br></div></div><div><div dir=3D"auto">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?</div=
></div><div><div dir=3D"auto"><br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:so=
lid;padding-left:1ex;border-left-color:rgb(204,204,204)"><br>
Does the problem occur on GNU/Linux as well?<br>
</blockquote><div dir=3D"auto"><br></div></div><div><div dir=3D"auto">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</div></div><div><div><div class=3D"gma=
il_quote"><div dir=3D"auto"><br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:soli=
d;padding-left:1ex;border-left-color:rgb(204,204,204)"><br>
Is it a recent regression of your LilyPond package for macOS?</blockquote><=
div dir=3D"auto"><br></div><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</div><div dir=3D"auto"><br></div><div dir=3D"auto">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</div><div dir=3D"auto"><br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(=
204,204,204)"><br>
<br>
Unfortunately, Guile 1.8 has been unmaintained for several years and its<br=
>
code base has almost nothing in common with that of 2.0 and later, so I<br>
won=E2=80=99t make any promises.</blockquote><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">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. :)</div=
><div dir=3D"auto"><br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding=
-left:1ex;border-left-color:rgb(204,204,204)"><br>
<br>
Thanks,<br>
Ludo=E2=80=99.<br>
</blockquote></div></div>
</div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"g=
mail_signature">Marnen Laibow-Koser
<a href=3D"mailto:marnen@HIDDEN">marnen@HIDDEN</a>
<a href=3D"http://www.marnen.org">http://www.marnen.org</a>

Sent from Gmail Mobile</div>

--00000000000060fdb405a0458f76--

Message sent to bug-guile@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#39863: Guile 1.8, apparent segfault on some Macs running Mojave
Resent-From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guile@HIDDEN
Resent-Date: Sat, 07 Mar 2020 20:37:01 +0000
Resent-Message-ID: <handler.39863.B39863.15836134041033 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 39863
X-GNU-PR-Package: guile
X-GNU-PR-Keywords: 
To: Marnen Laibow-Koser <marnen@HIDDEN>
Cc: Ivo Bouwmans <muziek@HIDDEN>, 39863 <at> debbugs.gnu.org
Received: via spool by 39863-submit <at> debbugs.gnu.org id=B39863.15836134041033
          (code B ref 39863); Sat, 07 Mar 2020 20:37:01 +0000
Received: (at 39863) by debbugs.gnu.org; 7 Mar 2020 20:36:44 +0000
Received: from localhost ([127.0.0.1]:47627 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1jAgBg-0000Gb-5a
	for submit <at> debbugs.gnu.org; Sat, 07 Mar 2020 15:36:44 -0500
Received: from eggs.gnu.org ([209.51.188.92]:33943)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <ludo@HIDDEN>) id 1jAgBe-0000GM-6G
 for 39863 <at> debbugs.gnu.org; Sat, 07 Mar 2020 15:36:43 -0500
Received: from fencepost.gnu.org ([2001:470:142:3::e]:43350)
 by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <ludo@HIDDEN>)
 id 1jAgBX-0007cF-Tj; Sat, 07 Mar 2020 15:36:35 -0500
Received: from [2a01:e0a:1d:7270:af76:b9b:ca24:c465] (port=34136 helo=ribbon)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <ludo@HIDDEN>)
 id 1jAgBW-0007fw-Lu; Sat, 07 Mar 2020 15:36:35 -0500
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
References: <CAKZYM4AM5VaZK3PYKRsV7sA0evpEo5kPvaZKCVeS+tGAS8Y0Bg@HIDDEN>
 <875zfgjj24.fsf@HIDDEN>
 <CAKZYM4BKJCOv2s5fG4KipS_BTw6u-dMFQ_FDHC0PQA2Go+bFjQ@HIDDEN>
X-URL: http://www.fdn.fr/~lcourtes/
X-Revolutionary-Date: 18 =?UTF-8?Q?Vent=C3=B4se?= an 228 de la =?UTF-8?Q?R=C3=A9volution?=
X-PGP-Key-ID: 0x090B11993D9AEBB5
X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc
X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4  0CFB 090B 1199 3D9A EBB5
X-OS: x86_64-pc-linux-gnu
Date: Sat, 07 Mar 2020 21:36:31 +0100
In-Reply-To: <CAKZYM4BKJCOv2s5fG4KipS_BTw6u-dMFQ_FDHC0PQA2Go+bFjQ@HIDDEN>
 (Marnen Laibow-Koser's message of "Sat, 7 Mar 2020 10:38:11 -0500")
Message-ID: <87o8t7gawg.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Spam-Score: -0.7 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.7 (-)

Hi,

Marnen Laibow-Koser <marnen@HIDDEN> skribis:

> On Sat, Mar 7, 2020 at 10:12 AM Ludovic Court=C3=A8s <ludo@HIDDEN> wrote:

[...]

>> Could you provide a backtrace of the segfault?
>>
>
> I=E2=80=99m not sure how I would be able to get any more detailed debuggi=
ng 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 =E2=80=9Cbt=E2=80=9D there=
 (apologies
if that info is already in the GitLab issue, I didn=E2=80=99t see it.)

>> 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*.

Ah OK.  Then perhaps you could look at how Homebrew, MacPorts &
co. package LilyPond in search of inspiration (speaking with my distro
hacker hat on :-))?

Thanks,
Ludo=E2=80=99.

Message sent to bug-guile@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#39863: Guile 1.8, apparent segfault on some Macs running Mojave
Resent-From: Marnen Laibow-Koser <marnen@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guile@HIDDEN
Resent-Date: Sat, 07 Mar 2020 21:44:02 +0000
Resent-Message-ID: <handler.39863.B39863.15836174337393 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 39863
X-GNU-PR-Package: guile
X-GNU-PR-Keywords: 
To: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
Cc: Ivo Bouwmans <muziek@HIDDEN>, 39863 <at> debbugs.gnu.org
Received: via spool by 39863-submit <at> debbugs.gnu.org id=B39863.15836174337393
          (code B ref 39863); Sat, 07 Mar 2020 21:44:02 +0000
Received: (at 39863) by debbugs.gnu.org; 7 Mar 2020 21:43:53 +0000
Received: from localhost ([127.0.0.1]:47699 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1jAhEe-0001vB-KN
	for submit <at> debbugs.gnu.org; Sat, 07 Mar 2020 16:43:52 -0500
Received: from mail-yw1-f41.google.com ([209.85.161.41]:42129)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <marnen@HIDDEN>) id 1jAgz2-0001Wb-UQ
 for 39863 <at> debbugs.gnu.org; Sat, 07 Mar 2020 16:27:45 -0500
Received: by mail-yw1-f41.google.com with SMTP id v138so5987837ywa.9
 for <39863 <at> debbugs.gnu.org>; Sat, 07 Mar 2020 13:27:44 -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=4dF9kaYLvnl6a/0nicLZD384LDQwqfqnY2Liea4GBc8=;
 b=On6seXyrh3hcBP8ejVRpVjG6iIGWIHN26TiOfJ4agvj3zH81OoGcIR6hGlbTzLRdDK
 TrPBriQ6as+v2AGLGl7qkGHmlSIFLw/IIpSnQpoh+9Xi69w4/Mhxpxja7TiqqRFv3E1U
 k39O2eWgj0Uh+yRW2Z4MWJ9hC9w4ThgwJc9f6R9ANRzhKumpN5PemjXXTYQIJoIqlkkv
 TNgwRIqXNfmc36up4SCiiTS12YPzKKnHdlbUlyk15hMTEOBUYdNDvBt9RVuKIp9vnXnV
 GCYUyQK+WQKYUmkRy1DYcRNedM0SxxOK9d0Y4GD5nzyLQonhTv3XTuDBrjYmRfywrbLa
 ex8A==
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=4dF9kaYLvnl6a/0nicLZD384LDQwqfqnY2Liea4GBc8=;
 b=B9j38z8gALBfIwPtzY4cHBUNe27NVdYDSsgAcS3wjItpo/E2cBUiT82jHYkrh9ImI3
 EBMDRC1rzBZOpL/WslUsr08sIt4qmH2Kb9okoVshIgspGT5M/fXY0tMtovQ+oXEY6ODn
 xqVyMZWxK1+V4F+tBA9cZgQg/IKNSjTRXf+M8o86bas5QWbZEHGbknn6UJqqi9I64YQJ
 uIVyoKU4dmmH6365q8EAfhM1gfNlK0qWArKdXObQunWl0rzgXebIKc7k8YD6JnuOjVRd
 5JhIY74U/f87wJNHagc+skJ8seclMljqVZui9wnL7zgPH97JUy2j3E6/AZDCBbYAnisD
 8yOw==
X-Gm-Message-State: ANhLgQ0wDHcMyiYjeZ9raVMLinXB3LJq81upeu0jGa2Wz0MaPMHn2wnj
 cWL+nI62oGFHDWWV2WRVfVq7QuSpKwmUzDzJp8idXYCIgLQ=
X-Google-Smtp-Source: ADFU+vuAxTfYQAL1XRDP/5Qzb3eCdaYwJ6t8v0oehmhzwrsn2A6MZDGzSlCBWPyBynRw1o8zhBXwsZCF0viMpUW8g6k=
X-Received: by 2002:a0d:f687:: with SMTP id
 g129mr11354397ywf.342.1583616457953; 
 Sat, 07 Mar 2020 13:27:37 -0800 (PST)
MIME-Version: 1.0
References: <CAKZYM4AM5VaZK3PYKRsV7sA0evpEo5kPvaZKCVeS+tGAS8Y0Bg@HIDDEN>
 <875zfgjj24.fsf@HIDDEN>
 <CAKZYM4BKJCOv2s5fG4KipS_BTw6u-dMFQ_FDHC0PQA2Go+bFjQ@HIDDEN>
 <87o8t7gawg.fsf@HIDDEN>
In-Reply-To: <87o8t7gawg.fsf@HIDDEN>
From: Marnen Laibow-Koser <marnen@HIDDEN>
Date: Sat, 7 Mar 2020 16:27:27 -0500
Message-ID: <CAKZYM4DiOBMY4q8+GANr0AaPGKtb_Q_fjDM2xePx9_oJMtcXtg@HIDDEN>
Content-Type: multipart/alternative; boundary="0000000000006fe85a05a04a7011"
X-Spam-Score: 0.0 (/)
X-Mailman-Approved-At: Sat, 07 Mar 2020 16:43:51 -0500
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

--0000000000006fe85a05a04a7011
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Mar 7, 2020 at 3:36 PM Ludovic Court=C3=A8s <ludo@HIDDEN> wrote:

> Hi,
>
> Marnen Laibow-Koser <marnen@HIDDEN> skribis:
>
> > On Sat, Mar 7, 2020 at 10:12 AM Ludovic Court=C3=A8s <ludo@HIDDEN> wro=
te:
>
> [...]
>
> >> Could you provide a backtrace of the segfault?
> >>
> >
> > I=E2=80=99m not sure how I would be able to get any more detailed debug=
ging info
> > than the logs that I posted in the GitLab issue.  Have you looked at
> > those?  Alternatively, is there an environment variable or anything tha=
t
> > would get Guile to provide more information when it does segfault?
>
> I would just run GDB on the dumped core, and run =E2=80=9Cbt=E2=80=9D the=
re (apologies
> if that info is already in the GitLab issue, I didn=E2=80=99t see it.)


It isn=E2=80=99t.  I rarely have to do this sort of debugging, so I didn=E2=
=80=99t really
know how to do it. Let me see what I can do, though I don=E2=80=99t know if=
 there
was an actual coredump.


>
> >> 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 eith=
er: this packaging
> > is newly developed, so there=E2=80=99s nothing to regress *from*.
>
> Ah OK.  Then perhaps you could look at how Homebrew, MacPorts &
> co. package LilyPond in search of inspiration (speaking with my distro
> hacker hat on :-))?


I did (you can see the lilypond-dev list archives if you=E2=80=99re really
interested in the gory details).  This packaging is the result of the
process of lots of research on how to actually make it all work for 64-bit
Mac OS=E2=80=94and it does work, except, consistently, for one particular u=
ser.


>
> Thanks,
> Ludo=E2=80=99.


Best,
--=20
Marnen Laibow-Koser marnen@HIDDEN http://www.marnen.org Sent from Gmail
Mobile

--0000000000006fe85a05a04a7011
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><br></div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Sat, Mar 7, 2020 at 3:36 PM Ludovic Court=C3=A8s &lt;<a =
href=3D"mailto:ludo@HIDDEN">ludo@HIDDEN</a>&gt; wrote:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-widt=
h:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,20=
4,204)">Hi,<br>
<br>
Marnen Laibow-Koser &lt;<a href=3D"mailto:marnen@HIDDEN" target=3D"_bla=
nk">marnen@HIDDEN</a>&gt; skribis:<br>
<br>
&gt; On Sat, Mar 7, 2020 at 10:12 AM Ludovic Court=C3=A8s &lt;<a href=3D"ma=
ilto:ludo@HIDDEN" target=3D"_blank">ludo@HIDDEN</a>&gt; wrote:<br>
<br>
[...]<br>
<br>
&gt;&gt; Could you provide a backtrace of the segfault?<br>
&gt;&gt;<br>
&gt;<br>
&gt; I=E2=80=99m not sure how I would be able to get any more detailed debu=
gging info<br>
&gt; than the logs that I posted in the GitLab issue.=C2=A0 Have you looked=
 at<br>
&gt; those?=C2=A0 Alternatively, is there an environment variable or anythi=
ng that<br>
&gt; would get Guile to provide more information when it does segfault?<br>
<br>
I would just run GDB on the dumped core, and run =E2=80=9Cbt=E2=80=9D there=
 (apologies<br>
if that info is already in the GitLab issue, I didn=E2=80=99t see it.)</blo=
ckquote><div dir=3D"auto"><br></div><div dir=3D"auto">It isn=E2=80=99t.=C2=
=A0 I rarely have to do this sort of debugging, so I didn=E2=80=99t really =
know how to do it. Let me see what=C2=A0I can do, though I don=E2=80=99t kn=
ow if there was an actual coredump.=C2=A0</div><div dir=3D"auto"><br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:r=
gb(204,204,204)"><br>
<br>
&gt;&gt; Is it a recent regression of your LilyPond package for macOS?<br>
&gt;<br>
&gt;<br>
&gt; I=E2=80=99m afraid that question doesn=E2=80=99t have much meaning eit=
her: this packaging<br>
&gt; is newly developed, so there=E2=80=99s nothing to regress *from*.<br>
<br>
Ah OK.=C2=A0 Then perhaps you could look at how Homebrew, MacPorts &amp;<br=
>
co. package LilyPond in search of inspiration (speaking with my distro<br>
hacker hat on :-))?</blockquote><div dir=3D"auto"><br></div><div dir=3D"aut=
o">I did (you can see the lilypond-dev list archives if you=E2=80=99re real=
ly interested in the gory details).=C2=A0 This packaging is the result of t=
he process of lots of research on how to actually make it all work for 64-b=
it Mac OS=E2=80=94and it does work, except, consistently, for one particula=
r user.=C2=A0</div><div dir=3D"auto"><br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-s=
tyle:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><br>
<br>
Thanks,<br>
Ludo=E2=80=99.</blockquote><div dir=3D"auto"><br></div><div dir=3D"auto">Be=
st,</div></div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" data=
-smartmail=3D"gmail_signature">Marnen Laibow-Koser
<a href=3D"mailto:marnen@HIDDEN">marnen@HIDDEN</a>
<a href=3D"http://www.marnen.org">http://www.marnen.org</a>

Sent from Gmail Mobile</div>

--0000000000006fe85a05a04a7011--

Last modified: Sat, 7 Mar 2020 21:45:01 UTC

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