Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

'use std' in module imported by crate corrupts things #125

Closed
jyasskin opened this issue Jul 25, 2010 · 1 comment
Closed

'use std' in module imported by crate corrupts things #125

jyasskin opened this issue Jul 25, 2010 · 1 comment

Comments

@jyasskin
Copy link
Contributor

$ cat ~/tmp/test.rc
use std;
mod driver;
$ cat ~/tmp/driver.rs
use std;
import std._vec;
fn main(vec[str] args) -> () {
  log ("args(0) == " + args.(0));
  log _vec.slice[str](args, 0, 1).(0);
}
$ ./rustboot -L . ~/tmp/test.rc -o ~/tmp/test && ~/tmp/test abc
rt: 0xa0563720:0xbfffec74:0x00100200:     upcall log_str("args(0) == /Users/jyasskin/tmp/test")
rt: fatal, 'leaked memory in rust main loop (2 objects)' failed, rt/rust.cpp:32

Commenting out the "use std;" in driver.rs fixes the leak and keeps running through the second log statement. I saw this first as a SIGBUS, but I suspect this reduction is the same bug.

@graydon
Copy link
Contributor

graydon commented Jan 27, 2011

WONTFIX (not required for bootstrapping).

oli-obk pushed a commit to oli-obk/rust that referenced this issue Jul 19, 2017
compute the offset of dst fields by checking the vtable
dlrobertson pushed a commit to dlrobertson/rust that referenced this issue Nov 29, 2018
Aaron1011 pushed a commit to Aaron1011/rust that referenced this issue Oct 26, 2020
bors pushed a commit to rust-lang-ci/rust that referenced this issue Oct 1, 2021
Remove extended_key_value_attributes feature
djtech-dev pushed a commit to djtech-dev/rust that referenced this issue Dec 9, 2021
Add IntValue::is_constant_int() which is true iff is_const() and the int value is not a constant expression.
bjorn3 pushed a commit to bjorn3/rust that referenced this issue Feb 1, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants