From e0f110aa12f7f5f99333b69b541a569e2a1d4041 Mon Sep 17 00:00:00 2001 From: Jeff Olson Date: Mon, 16 Apr 2012 15:29:07 -0700 Subject: 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.. --- src/rt/rust_kernel.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/rt/rust_kernel.cpp') 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 -- cgit 1.4.1-3-g733a5