CI: Test on Windows #4
Assignees
Comments
|
Done in #9 |
da-x
added a commit
to da-x/compiler-builtins
that referenced
this issue
Jul 23, 2019
In order for GDB to correctly backtrace a stack overflow, it needs CFI information in __rust_probestack. This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/github.com-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this issue
Jul 23, 2019
In order for GDB to correctly backtrace a stack overflow, it needs CFI information in __rust_probestack. This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/github.com-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this issue
Jul 23, 2019
In order for GDB to correctly backtrace a stack overflow, it needs CFI information in __rust_probestack. This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/github.com-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this issue
Jul 23, 2019
In order for GDB to correctly backtrace a stack overflow, it needs CFI information in __rust_probestack. This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/github.com-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this issue
Jul 23, 2019
In order for GDB to correctly backtrace a stack overflow, it needs CFI information in __rust_probestack. This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/github.com-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this issue
Jul 23, 2019
In order for GDB to correctly backtrace a stack overflow, it needs CFI information in __rust_probestack. This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/github.com-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this issue
Jul 24, 2019
This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/github.com-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this issue
Jul 24, 2019
This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/github.com-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We could use AppVeyor but its build cycles are pretty slow. I guess we can start with 64-bit mingw on Travis to keep the test times small.
The text was updated successfully, but these errors were encountered: