Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

"rustc" with no arguments crashes #155

Closed
pcwalton opened this issue Aug 27, 2010 · 1 comment
Closed

"rustc" with no arguments crashes #155

pcwalton opened this issue Aug 27, 2010 · 1 comment

Comments

@pcwalton
Copy link
Contributor

[pwalton@host-4-94 ~/Source/rust/src] ./rustc
rt: ---
rt: 2d2d:main:main:                       rust: This is the rust 'self-hosted' compiler.
rt: 2d2d:main:main:                       rust: The one written in rust.
rt: 2d2d:main:main:                       rust: It does nothing yet, it's a placeholder.
rt: 2d2d:main:main:                       rust: You want rustboot, the compiler next door.
free: ptr 0x100360 is not in allocation_list
rt: fatal, 'not in allocation_list' failed, rt/memory_region.cpp:28 

froystig says this is due to "argv" not bounds checking like real arrays do.

@graydon
Copy link
Contributor

graydon commented Jan 27, 2011

Fixed long ago. 'rustc' alone still hits a 'fail' path, but not due to a runtime crash.

pcwalton added a commit to pcwalton/rust that referenced this issue Sep 13, 2014
type they provide an implementation for.

This breaks code like:

    mod foo {
        struct Foo { ... }
    }

    impl foo::Foo {
        ...
    }

Change this code to:

    mod foo {
        struct Foo { ... }

        impl Foo {
            ...
        }
    }

Additionally, if you used the I/O path extension methods `stat`,
`lstat`, `exists`, `is_file`, or `is_dir`, note that these methods have
been moved to the the `std::io::fs::PathExtensions` trait. This breaks
code like:

    fn is_it_there() -> bool {
        Path::new("/foo/bar/baz").exists()
    }

Change this code to:

    use std::io::fs::PathExtensions;

    fn is_it_there() -> bool {
        Path::new("/foo/bar/baz").exists()
    }

Closes rust-lang#17059.

RFC rust-lang#155.

[breaking-change]
bors added a commit that referenced this issue Sep 14, 2014
…hton

type they provide an implementation for.

This breaks code like:

    mod foo {
        struct Foo { ... }
    }

    impl foo::Foo {
        ...
    }

Change this code to:

    mod foo {
        struct Foo { ... }

        impl Foo {
            ...
        }
    }

Closes #17059.

RFC #155.

[breaking-change]

r? @brson
arielb1 pushed a commit to arielb1/rust that referenced this issue Apr 10, 2015
In particular:

* The RFC associated with rust-lang#127 should have had a link to rust-lang#19 as well
  (and has been assigned RFC rust-lang#19); it also was revised to match the
  markdown href style of other RFCs.

* RFC rust-lang#34 needed its header entries filled in,

* RFC rust-lang#123 had a typo in its header, and

* RC rust-lang#155 was revised to match the markdown href style of other RFCs.
oli-obk pushed a commit to oli-obk/rust that referenced this issue Jul 19, 2017
remove feature opt-ins that are no longer needed
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
kazcw pushed a commit to kazcw/rust that referenced this issue Oct 23, 2018
* x86: implemented maskloads for avx2

* x86: added docs and tests for avx2 maskloads

* x86: refactor - changed `a` to `mem_addr` in avx2 mask loads for consistency

* x86: implemented _mm{,256}_maskstore_epi{32,64}
bors pushed a commit to rust-lang-ci/rust that referenced this issue Oct 1, 2021
* Fix cargo features for nightly
djtech-dev pushed a commit to djtech-dev/rust that referenced this issue Dec 9, 2021
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
This issue was closed.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants