From: Efraim Flashner <efraim@flashner.co.il>
To: Sam Lockart <samlockart@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Segmentation fault when running rust-cargo
Date: Mon, 29 May 2023 21:08:55 +0300 [thread overview]
Message-ID: <ZHTqN-CaX-RCL3P2@3900XT> (raw)
In-Reply-To: <CAERTYwd65owjEFV_WV_Qg_SpaqtJOFwx7-b3wzQQN2c7kj28Gg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
On Thu, May 25, 2023 at 07:19:07AM +0000, Sam Lockart wrote:
> I am trying to run `cargo update` (version 1.59.0) on a rust project but am
> encountering a segmentation fault.
What version of cargo are you running? The 'cargo' binary from the cargo
output of rust is 1.67.1 currently.
> =2D-8<---------------cut here---------------start------------->8---
> (gdb) run update
> Starting program:
> /gnu/store/3p1vy8lqx0fazck9gnmk0dlp6hni3zqs-profile/bin/cargo update
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library
> "/gnu/store/gsjczqir1wbz8p770zndrpw4rnppmxi3-glibc-2.35/lib/libthread_db.so.1".
> Updating crates.io index
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7f48128 in ?? () from
> /gnu/store/kqcv7w297aihagjdj3pqkxd4ssdxnx4f-libgit2-1.5.1/lib/libgit2.so.1.5
> (gdb) bt
> #0 0x00007ffff7f48128 in ?? () from
> /gnu/store/kqcv7w297aihagjdj3pqkxd4ssdxnx4f-libgit2-1.5.1/lib/libgit2.so.1.5
> #1 0x00007ffff7f49db5 in git_remote_fetch () from
> /gnu/store/kqcv7w297aihagjdj3pqkxd4ssdxnx4f-libgit2-1.5.1/lib/libgit2.so.1.5
<snip>
> Thank you in advance!
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-05-29 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 7:19 Segmentation fault when running rust-cargo Sam Lockart
2023-05-29 18:08 ` Efraim Flashner [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
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=ZHTqN-CaX-RCL3P2@3900XT \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=samlockart@gmail.com \
/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).