From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Rust 1.19 fails to build on i686 on ‘staging’
Date: Tue, 29 Jan 2019 09:36:32 +0100 [thread overview]
Message-ID: <877eenrhbj.fsf@gnu.org> (raw)
In-Reply-To: <20190128162705.052961e4@scratchpost.org> (Danny Milosavljevic's message of "Mon, 28 Jan 2019 16:27:05 +0100")
Hi Danny,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Mon, 28 Jan 2019 15:39:33 +0100
> Ludovic Courtès <ludo@gnu.org> wrote:
>> > /gnu/store/fw4yy7cgb5ahs9s2ir00bawnsl5zj7db-mrustc-0.8.0/bin/mrustc[...]
>> munmap_chunk(): invalid pointer
>
> Maybe the above causes
>
>> src/tools/cargo/src/crates-io/lib.rs:65: BUG:src/expand/proc_macro.cpp:941: Unexpected EOF while reading from child process
>
> this.
>
> Might be a memory double-free. Exactly the kind of thing that Rust is supposed
> to prevent is in the Rust compiler in C++ - well, at least the motivation for
> having Rust is clear now ;-)
Heh, sounds like it.
> Can you try just
>
> $ /gnu/store/fw4yy7cgb5ahs9s2ir00bawnsl5zj7db-mrustc-0.8.0/bin/mrustc src/tools/cargo/src/crates-io/lib.rs --crate-name crates_io --crate-type rlib --crate-tag 0_9_0 -g --cfg debug_assertions -O -o output/cargo-build/libcrates_io-0_9_0.hir -L output/cargo-build --extern curl=output/cargo-build/libcurl-0_4_6.hir --extern error_chain=output/cargo-build/liberror_chain-0_10_0.hir --extern serde=output/cargo-build/libserde-1_0_6.hir --extern serde_derive=output/cargo-build/libserde_derive-1_0_6.hir --extern serde_json=output/cargo-build/libserde_json-1_0_2.hir --extern url=output/cargo-build/liburl-1_4_0.hir -L output -L /gnu/store/fw4yy7cgb5ahs9s2ir00bawnsl5zj7db-mrustc-0.8.0/lib/mrust
>
> in the build-failed kept source? (possibly with "ulimit -c unlimited" so it dumps core. mrustc is a normal C++ program, so normal debugging ways apply)
>
> Or do I have access to the machine so I can do it?
I don’t know but you could try:
guix build rust@1.19 -s i686-linux -K
on your x86_64 machine from ‘staging’, and hopefully you’ll get that
error too.
> Possible use-after free fix in mrustc commits:
>
> https://github.com/thepowersgang/mrustc/commit/a51eea542ae086687ea2c4cb09321785f5cc6269
Could be! We know what to try next.
Thanks for investigating!
Ludo’.
next prev parent reply other threads:[~2019-01-29 8:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 14:39 Rust 1.19 fails to build on i686 on ‘staging’ Ludovic Courtès
2019-01-28 15:22 ` Danny Milosavljevic
2019-01-28 15:27 ` Danny Milosavljevic
2019-01-28 15:35 ` Danny Milosavljevic
2019-01-29 8:36 ` Ludovic Courtès [this message]
2019-01-30 17:59 ` Danny Milosavljevic
2019-02-05 11:28 ` Danny Milosavljevic
2019-02-05 11:35 ` Danny Milosavljevic
2019-02-11 21:34 ` Danny Milosavljevic
2019-02-12 11:47 ` Chris Marusich
2019-02-12 12:06 ` Danny Milosavljevic
2019-02-13 2:59 ` Chris Marusich
2019-02-13 5:49 ` Chris Marusich
2019-02-14 4:35 ` Chris Marusich
2019-02-14 17:14 ` Danny Milosavljevic
2019-02-15 9:11 ` Chris Marusich
2019-02-15 10:51 ` Danny Milosavljevic
2019-02-16 10:53 ` Chris Marusich
2019-02-18 14:38 ` Danny Milosavljevic
2019-05-24 13:55 ` Danny Milosavljevic
2019-07-19 5:53 ` Chris Marusich
2019-07-21 17:53 ` Ricardo Wurmus
2019-01-28 15:50 ` Danny Milosavljevic
2019-01-28 18:41 ` Ricardo Wurmus
2019-01-28 20:25 ` Danny Milosavljevic
2019-01-31 5:51 ` Mark H Weaver
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=877eenrhbj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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.