search for: st_lookup

...uce, start the sample, select the first item in the widget tree list ("wxDialog"). Then close the Dialog with either the OK or Cancel button. Backtrace is: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0xb84352ec 0x00136e80 in st_lookup () (gdb) whe #0 0x00136e80 in st_lookup () #1 0x000cfe3c in rb_clear_cache_by_class () #2 0x000dac7d in rb_eval_string_wrap () #3 0x000d80da in rb_eval_string_wrap () #4 0x000d7c78 in rb_eval_string_wrap () #5 0x000d7c78 in rb_eval_string_wrap () #6 0x000d6a20 in rb_eval_string_wrap () #7 0...

...-84,20 +84,6 @@ let rec generate_ruby_c () = > #define RSTRING_PTR(r) (RSTRING((r))->ptr) > #endif > > -/* For RHEL 5 (Ruby 1.8.5) */ > -#ifndef HAVE_RB_HASH_LOOKUP > -VALUE > -rb_hash_lookup (VALUE hash, VALUE key) > -{ > - volatile VALUE val; > - > - if (!st_lookup (RHASH(hash)->tbl, key, &val)) > - return Qnil; > - > - return val; > -} > -#endif /* !HAVE_RB_HASH_LOOKUP */ The have_func("rb_hash_lookup") in ruby/ext/guestfs/extconf.rb.in could be removed then. Thanks, -- Pino Toscano

...d, this is a new one to me, so you aren''t going to find anything about it in the FXRuby documentation. > P.S: Here is a copy of what is writen to ruby1.8.crash.log: <snip> I scanned the stack trace, and it looks like the FXRuby code was trying to call an internal Ruby function (st_lookup) when it failed. I have a hunch that that interface has changed a bit since Ruby 1.8.1 (which is several years old now). My advice is to upgrade to the most recent version of Ruby (1.8.5), and then recompile FXRuby and try again. You shouldn''t need to recompile FOX -- just zap your FXRuby...

...644 --- a/generator/ruby.ml +++ b/generator/ruby.ml @@ -84,20 +84,6 @@ let rec generate_ruby_c () = #define RSTRING_PTR(r) (RSTRING((r))->ptr) #endif -/* For RHEL 5 (Ruby 1.8.5) */ -#ifndef HAVE_RB_HASH_LOOKUP -VALUE -rb_hash_lookup (VALUE hash, VALUE key) -{ - volatile VALUE val; - - if (!st_lookup (RHASH(hash)->tbl, key, &val)) - return Qnil; - - return val; -} -#endif /* !HAVE_RB_HASH_LOOKUP */ - static VALUE m_guestfs; /* guestfs module */ static VALUE c_guestfs; /* guestfs_h handle */ static VALUE e_Error; /* used for all errors */ diff --git a/run.in b/run.in index 42...

Here are three patches that fix issues with out-of-tree building and one that uses Ruby's own autoconf stuff for determining how Ruby bindings should be built. Cheers, -Hilko

Hi I''d like to put out a 1.9.3 release perhaps later this week/weekend. If you have a chance to test the build and samples esp with latest rubygems, please do. There are still some bugs on the list, and samples to do, but this should address all the build/install probs that have come up. And it would be good to get some testing and feedback on some of the new classes. A note on the

I have a Rails 1.2.3 app (due for an update, I know) running on a Mongrel 1.1.4 behind Apache 2.2.3 mod_proxy on Debian 4.0. It keeps hanging up for no reason I can tell. I have tried everything that anyone has ever hinted at being a solution for this problem: - The application doesn''t use MySQL, so setting the connection timeout won''t help. - Using AR not PStore for sessions. -