rustc nightly returns 1 (false) on armv7

[belst]

I tried compiling a project of mine on my raspberry pi 2 but I couldnt, because rustc always crashed.

After Investigating a bit further I found this out:

fn main() {
    println!("hello");
}

this DOES NOT compile

pi@babylon5 ~/foo/src (git)-[master] % RUST_BACKTRACE=1 rustc --verbose main.rs
1 pi@babylon5 ~/foo/src (git)-[master] % ls                                                                                                         :(
main.rs

this however, DOES compile:

fn main() {
    std::process::exit(5);
}

output:

pi@babylon5 ~/foo/src (git)-[master] % RUST_BACKTRACE=1 rustc --verbose main.rs
pi@babylon5 ~/foo/src (git)-[master] % ls
main  main.rs
pi@babylon5 ~/foo/src (git)-[master] % ./main
5 pi@babylon5 ~/foo/src (git)-[master] %                                                                                                            :(

Meta

rustc --version --verbose:

rustc 1.13.0-nightly (3c5a0fa45 2016-08-22)
binary: rustc
commit-hash: 3c5a0fa45b5e2786b6e64e27f48cd129e7aefdbd
commit-date: 2016-08-22
host: armv7-unknown-linux-gnueabihf
release: 1.13.0-nightly

uname -a:

Linux babylon5 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux

[durka]

Since it seems to be aborting with no output or backtrace, can you try running it under a debugger to see where it stops?

[belst]

(gdb) run main.rs
Starting program: /home/pi/.cargo/bin/rustc main.rs
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[Inferior 1 (process 31513) exited with code 01]

[durka]

And bt doesn't give any hints?

On Thu, Aug 25, 2016 at 11:25 AM, Joshua notifications@github.com wrote:

(gdb) run main.rs
Starting program: /home/pi/.cargo/bin/rustc main.rs
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[Inferior 1 (process 31513) exited with code 01]

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#35982 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAC3n3Bq2QUbQ0_VTaag7fpt_SIMd_E0ks5qjbPOgaJpZM4Js8AR
.

[belst]

no stack
single stepping through gives this:

(gdb) next
Single stepping until exit from function main,
which has no line number information.
0x54dce7cc in std::rt::lang_start::hb072ea7464d45b94 ()
(gdb) next
Single stepping until exit from function _ZN3std2rt10lang_start17hb072ea7464d45b94E,
which has no line number information.
[Inferior 1 (process 31570) exited with code 01]

(gdb) bt
#0  0x54b28d34 in main ()
(gdb) next
Single stepping until exit from function main,
which has no line number information.
0x54dce7cc in std::rt::lang_start::hb072ea7464d45b94 ()
(gdb) bt
#0  0x54dce7cc in std::rt::lang_start::hb072ea7464d45b94 ()
#1  0x76e12294 in __libc_start_main (main=0x7efff5e4, argc=1995665408, argv=0x76e12250 <__libc_start_main+208>, init=<optimized out>, 
    fini=0x54df9615 <__libc_csu_fini>, rtld_fini=0x76fdf408 <_dl_fini>, stack_end=0x7efff5e4) at libc-start.c:287
#2  0x54aed04e in _start ()
(gdb) next
Single stepping until exit from function _ZN3std2rt10lang_start17hb072ea7464d45b94E,
which has no line number information.
[Inferior 1 (process 31582) exited with code 01]
(gdb) bt
No stack.
(gdb) 

[durka]

It seems like the compiler doesn't even start.

On Thu, Aug 25, 2016 at 11:31 AM, Joshua notifications@github.com wrote:

no stack
single stepping through gives this:

(gdb) next
Single stepping until exit from function main,
which has no line number information.
0x54dce7cc in std::rt::lang_start::hb072ea7464d45b94 ()
(gdb) next
Single stepping until exit from function _ZN3std2rt10lang_start17hb072ea7464d45b94E,
which has no line number information.
[Inferior 1 (process 31570) exited with code 01]

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#35982 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAC3n6SF6I8cYwsX8xFOIWbkzYFCEVFfks5qjbVIgaJpZM4Js8AR
.

[belst]

well it works on the std::process::exit() example

[MagaTailor]

Did you manage to run rustc -vV? If not, look for a patchelf workaround a dozen issues earlier.

[belst]

@petevine yes. I have seen the other issue. but running rustc -vV succeeds

[MagaTailor]

Right, sorry;missed the meta info. If you're using an official build, try the workaround all the same or use a different nightly. Definitely works for me.

[belst]

just updated rustc to latest nightly

rustc 1.13.0-nightly (e9bc1bac8 2016-08-24)
binary: rustc
commit-hash: e9bc1bac8c7664fb1b487879b3fbd56221f6a721
commit-date: 2016-08-24
host: armv7-unknown-linux-gnueabihf
release: 1.13.0-nightly

still no change. stable works btw.

[MagaTailor]

Could you try a recent build of mine? If that doesn't work either, rustc is not to blame.

[belst]

your build works.

[MagaTailor]

Aha, hopefully a variation of that patchelf issue. It would be ridiculous if the buildbot binaries didn't work for some new reason!

[belst]

the patchelf workaround described in #35843 does not work and I do not get a segfault.