You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running cargo build followed by executing the binary prints: Segmentation fault (core dumped).
In contrast, running cargo run gives no textual indication of the failure. The output displayed is:
Thanks for the report! Cargo just calls exec, however, on the binary ./three. In that sense it's up to your shell to report segfault information, but this is likely being swallowed by rustup, so I'm going to close in favor of that issue.
With the following program, which causes a segmentation fault by allocating too much on the stack:
Running
cargo build
followed by executing the binary prints:Segmentation fault (core dumped)
.In contrast, running
cargo run
gives no textual indication of the failure. The output displayed is:This is using either of cargo 0.16.0 and 0.15.0 on Ubuntu Linux 14.04
The text was updated successfully, but these errors were encountered: