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 16:27:27 -0500 Message-ID: References: <875zfgjj24.fsf@gnu.org> <87o8t7gawg.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000006fe85a05a04a7011" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="6083"; 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 22:44:13 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 1jAhEy-0001TZ-O2 for guile-bugs@m.gmane-mx.org; Sat, 07 Mar 2020 22:44:12 +0100 Original-Received: from localhost ([::1]:52976 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jAhEx-0008MM-DR for guile-bugs@m.gmane-mx.org; Sat, 07 Mar 2020 16:44:11 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56807) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jAhEq-0008M8-1g for bug-guile@gnu.org; Sat, 07 Mar 2020 16:44:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jAhEo-0003ZV-Nx for bug-guile@gnu.org; Sat, 07 Mar 2020 16:44:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:41726) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jAhEo-0003Z6-8K for bug-guile@gnu.org; Sat, 07 Mar 2020 16:44:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jAhEo-0001vg-5V for bug-guile@gnu.org; Sat, 07 Mar 2020 16:44: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 21:44:02 +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.15836174337393 (code B ref 39863); Sat, 07 Mar 2020 21:44:02 +0000 Original-Received: (at 39863) by debbugs.gnu.org; 7 Mar 2020 21:43:53 +0000 Original-Received: from localhost ([127.0.0.1]:47699 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jAhEe-0001vB-KN for submit@debbugs.gnu.org; Sat, 07 Mar 2020 16:43:52 -0500 Original-Received: from mail-yw1-f41.google.com ([209.85.161.41]:42129) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jAgz2-0001Wb-UQ for 39863@debbugs.gnu.org; Sat, 07 Mar 2020 16:27:45 -0500 Original-Received: by mail-yw1-f41.google.com with SMTP id v138so5987837ywa.9 for <39863@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) In-Reply-To: <87o8t7gawg.fsf@gnu.org> X-Mailman-Approved-At: Sat, 07 Mar 2020 16:43:51 -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:9627 Archived-At: --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 wrote: > Hi, > > Marnen Laibow-Koser skribis: > > > On Sat, Mar 7, 2020 at 10:12 AM Ludovic Court=C3=A8s 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@marnen.org http://www.marnen.org Sent from Gmail Mobile --0000000000006fe85a05a04a7011 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


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

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

> On Sat, Mar 7, 2020 at 10:12 AM Ludovic Court=C3=A8s <ludo@gnu.org> 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 debu= gging info
> 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 anythi= ng 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.)

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

=


>> 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 eit= her: this packaging
> is newly developed, so there=E2=80=99s nothing to regress *from*.

Ah OK.=C2=A0 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 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



Thanks,
Ludo=E2=80=99.

Be= st,
--
Marnen Laibow-Koser marnen@marnen.org http://www.marnen.org Sent from Gmail Mobile
--0000000000006fe85a05a04a7011--