From: Christopher Baines <mail@cbaines.net>
To: Christopher Baines <mail@cbaines.net>
Cc: 63445@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#63445: guix-build-coordinator guile-gnutls segfault
Date: Sat, 02 Sep 2023 11:33:17 +0100 [thread overview]
Message-ID: <87pm30euer.fsf@cbaines.net> (raw)
In-Reply-To: <87wn14d76l.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hi,
>>
>> Christopher Baines <mail@cbaines.net> skribis:
>>
>>> I've seen the build coordinator on bayfront crash a couple of times, and
>>> it seems to be segfaulting, maybe in gnutls?
>>>
>>> May 11 14:31:39 localhost vmunix: [15795370.287670]
>>> build-submitted[6013]: segfault at 0 ip 00007f1e2e796415 sp
>>> 00007f1b86ffd640 error 4 in
>>> guile-gnutls-v-2.so.0.0.0[7f1e2e790000+17000]
>>> May 11 14:31:39 localhost vmunix: [15795370.287692] Code: 01 00 41
>>> 0f b7 14 24 48 3b 10 0f 85 85 00 00 00 49 8b 6c 24 08 48 89 f3 48 89
>>> ef e8 d5 9d ff ff 4c 8b 68 08 41 f6 c5 06 75 0d <49> 8b 45 00 83 e0
>>> 7f 48 83 f8 7d 74 3a 31 f6 bf 10 00 00 00 e8 c2
>>
>> Did you manage to get a backtrace?
>
> Not yet, I've been trying to change the core file size limit with the
> prlimit command, but I haven't seen any core dump files yet, so I'm not
> sure if I've missed something.
I've finally managed to get core dumps working for this now, and I've
reported the problem upstream.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2023-09-02 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 12:52 bug#63445: guix-build-coordinator guile-gnutls segfault Christopher Baines
2023-05-18 17:59 ` Ludovic Courtès
2023-05-19 9:01 ` Christopher Baines
2023-09-02 10:33 ` Christopher Baines [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pm30euer.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=63445@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.