diff options
| author | Jeff Olson <olson.jeffery@gmail.com> | 2012-04-16 15:29:07 -0700 |
|---|---|---|
| committer | Brian Anderson <banderson@mozilla.com> | 2012-04-20 15:23:22 -0700 |
| commit | e0f110aa12f7f5f99333b69b541a569e2a1d4041 (patch) | |
| tree | 32879801cb32bbb8984d1dd29191d640fd322dca /src/rt/rust_kernel.cpp | |
| parent | 31ba223c26824ed26d8f848b307d599ab24a733b (diff) | |
| download | rust-e0f110aa12f7f5f99333b69b541a569e2a1d4041.tar.gz rust-e0f110aa12f7f5f99333b69b541a569e2a1d4041.zip | |
clean and trying the global loop test as two separate loop lifetimes..
.. seeing an occasional valgrind/barf spew on some invalid read/writes.. need to investigate further.. i think its related to my poor citizen conduct, re: pointers stashed in rust_kernel..
Diffstat (limited to 'src/rt/rust_kernel.cpp')
| -rw-r--r-- | src/rt/rust_kernel.cpp | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/rt/rust_kernel.cpp b/src/rt/rust_kernel.cpp index 2a4315bd842..adc62053345 100644 --- a/src/rt/rust_kernel.cpp +++ b/src/rt/rust_kernel.cpp @@ -27,8 +27,8 @@ rust_kernel::rust_kernel(rust_env *env) : // set up storage of pointers needed to // access the global loop. global_loop_chan = 0; - global_async_handle = (void**)::malloc( // FIXME -- can use this->malloc() - sizeof(void*)); // .. what do? + global_async_handle = (void**)::malloc( // FIXME--can't use this->malloc() + sizeof(void*)); // .. what do? *global_async_handle = (void*)0; // Create the single threaded scheduler that will run on the platform's |