From: Ricardo Wurmus <rekado@elephly.net>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 34616@debbugs.gnu.org
Subject: bug#34616: neovim segfaults
Date: Fri, 22 Feb 2019 16:57:19 +0100 [thread overview]
Message-ID: <8736of4y00.fsf@elephly.net> (raw)
In-Reply-To: <04f4ff1028b0defe4de7d72236f07a90@lepiller.eu>
Julien Lepiller <julien@lepiller.eu> writes:
> This is where I got neovim from:
>
> téléchargement depuis
> https://berlin.guixsd.org/nar/gzip/d8ibld5vpsgq7is3k3sf5gqj0i7sgmbh-neovim-0.3.4...
I built neovim locally. The binary contents differ from the files on
berlin. So there are two problems:
- neovim does not build reproducibly
- one of the builds segfaults
Have you tried running it in gdb to get a backtrace?
--
Ricardo
next prev parent reply other threads:[~2019-02-22 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 13:06 bug#34616: neovim segfaults Julien Lepiller
2019-02-22 15:06 ` Ricardo Wurmus
2019-02-22 15:13 ` Julien Lepiller
2019-02-22 15:57 ` Ricardo Wurmus [this message]
2019-02-22 16:35 ` Julien Lepiller
2019-02-22 17:11 ` Ricardo Wurmus
2019-02-24 9:02 ` Efraim Flashner
2019-03-01 16:31 ` Ricardo Wurmus
2019-03-05 19:53 ` Bradley Haggerty
[not found] <CAE4v=pg1YHwn4_xqJCpARYyn2qY1qK=o_aX6zB2fsGLN6je53A@mail.gmail.com>
2019-03-07 10:25 ` Gábor Boskovits
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736of4y00.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=34616@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).