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 21:36:31 +0100	[thread overview]
Message-ID: <87o8t7gawg.fsf@gnu.org> (raw)
In-Reply-To: <CAKZYM4BKJCOv2s5fG4KipS_BTw6u-dMFQ_FDHC0PQA2Go+bFjQ@mail.gmail.com> (Marnen Laibow-Koser's message of "Sat, 7 Mar 2020 10:38:11 -0500")

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

>> Is it a recent regression of your LilyPond package for macOS?
>
>
> I’m afraid that question doesn’t have much meaning either: this packaging
> is newly developed, so there’s 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’.





  reply	other threads:[~2020-03-07 20:36 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 [this message]
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=87o8t7gawg.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).