[#10830] New kill_thread function in eval.c conflict with a BeOS system function — <noreply@...>
Bugs item #9736, was opened at 01/04/2007 16:20
[#10834] Hefty patch for mkmf.rb — <noreply@...>
Patches item #9762, was opened at 2007-04-02 09:55
[#10853] Why limit class def to a constant or colon node? — Charles Oliver Nutter <charles.nutter@...>
Is there a historical reason why I can't do something like these:
Hi,
On 4/3/07, Charles Oliver Nutter <charles.nutter@sun.com> wrote:
[#10867] defined? operator changed in ruby 1.9: bug or feature? — David Flanagan <david@...>
The behavior of the defined? operator is different in current ruby 1.9
Hi,
[#10875] Ruby shouldn't process shebang! — "Kirill A. Shutemov" <k.shutemov@...>
> echo -e '#!test\nputs "test passed"' | ruby=20
On 4/5/07, Kirill A. Shutemov <k.shutemov@gmail.com> wrote:
[#10884] Ruby 1.9/1.8 compatibility: String#lines — murphy <murphy@...>
It seems the most important change in 1.9, in terms of compatibility, is
[#10907] install (/bin/install) path hardcoded at build — <noreply@...>
Bugs item #10004, was opened at 2007-04-10 13:21
[#10909] Turning off verbose output for mkmf — Daniel Berger <Daniel.Berger@...>
Hi all,
[#10923] block_given? => true in main(). — "Adam Bozanich" <adam.boz@...>
Hi all.
[#10933] Cannot build with extra library path if previous version already installed — <noreply@...>
Bugs item #10140, was opened at 2007-04-16 17:32
Hi,
On 4/16/07, nobu@ruby-lang.org <nobu@ruby-lang.org> wrote:
Hi,
On 4/19/07, Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:> Hi,>> At Wed, 18 Apr 2007 20:21:44 +0900,> Michal Suchanek wrote in [ruby-core:10960]:> > Yes. And this should also apply to extensions. The mkmf tests are now> > fine but the extension is linked with -L/sw/lib before -L../..>> Indeed.>>> Index: configure.in> ===================================================================> --- configure.in (revision 12191)> +++ configure.in (working copy)> @@ -1385,5 +1385,4 @@ if test "$enable_rpath" = yes; then> fi>> -LDFLAGS="-L. $LDFLAGS"> AC_SUBST(ARCHFILE)>This would break the previous fix so I did not even try to apply this ^
Hi,
[#10944] IRHG - "Three Stuffing" — Charles Thornton <ceo@...>
Can a japanese speaker give a translation
[#10947] backwards compatibility for 'raise Interrupt' — Ryan Davis <ryand-ruby@...>
** BEFORE:
Hi,
Hi,
[#10968] IRHG - Manuscript Hunt — Charles Thornton <ceo@...>
Does anyone know of a Text Copy (Not PDF) of this manuscript:
[#10981] ruby 1.9 crash on cygwin — "Anton Ivanov" <Anton.Ivanov@...>
Hi,
[#11003] miniruby loads extensions from already installed ruby — <noreply@...>
Bugs item #10303, was opened at 2007-04-23 10:44
Hi,
On 23/04/07, Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:
Hi,
On 26/04/07, Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:
Hi,
[#11012] Ruby 1.9: multiple splats on rvalues in parallel assignment — David Flanagan <david@...>
This has got to be a bug...
[#11025] gsub with backslash characters in replacement string — "Adam Bozanich" <adam.boz@...>
Hello, spotted this one the other day:
Hi,
On 4/26/07, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
On 4/26/07, Adam Bozanich <adam.boz@gmail.com> wrote:
On 4/26/07, Marte Raphael Y. Soliza <myrtactle@gmail.com > wrote:
[#11029] Proc#arity regression or bug in RDoc — Mauricio Fernandez <mfp@...>
On Thu, Apr 26, 2007 at 06:55:46PM +0900, Mauricio Fernandez wrote:
Stack problems with embedded ruby
Okay, I did a little bit more digging into ruby's source code (both 1.8 and 1.9), and it seems the problem lies in Init_stack() (and its cousin ruby_init_stack in later ruby versions) within gc.c. Currently, Init_stack() does not guarantee that the stack is reset. Ruby seems to do a bounds check first and only then decides whether to reset its internal variable (rb_gc_stack_start). This can easily lead ruby to think the stack is about to overflow and raise a stack error on an embedded ruby where ruby functions are called from drastically different addresses in memory. Unfortunately, for an embedded application, this is problematic. You really want ruby_init_stack() to init the stack to the address passed and not do the bounds check. Or is that the bounds check is being incorrectly done (reversed) on x86-64 AMD machines? When I remove the bounds check, all works as expected. Can anyone explain the logic of the current behavior? --- Here's a sample run of what happens with an embedded ruby where some methods are being called as callbacks from C++: >>> Embedded ruby is inited (and some basic config stuff is run) ruby_init_stack: (nil) at START ruby_init_stack: should reset to 0x7fffb12eb980 ruby_init_stack: 0x7fffb12eb980 at END Init_stack: 0x7fffb12eb980 at START Init_stack should reset to: 0x7fffb12eb964 Init_stack: 0x7fffb12eb980 at END mark stack 0x7fffb12eb980 - 0x7fffb12e7820- MARKED Starting Rendering /home/gga/maya/projects/default/images/untitled.iff. Rendering current frame. >>> >>> Render begins >>> shader's callback is called, ruby_init_stack(&localvar) is used >>> to reset stack, but it fails to do so. >>> ruby_init_stack: 0x7fffb12eb980 at START ruby_init_stack: should reset to 0x418021d0 ruby_init_stack: 0x7fffb12eb980 at END -- **NOT RESET** ruby_init_stack: 0x7fffb12eb980 at START ruby_init_stack: should reset to 0x418021d0 ruby_init_stack: 0x7fffb12eb980 at END -- **NOT RESET** Error: [Ruby] - /usr/local/lib/ruby/1.8/complex.rb:107:in `generic?' ....etc.... -- Gonzalo Garramu ggarra@advancedsl.com.ar AMD4400 - ASUS48N-E GeForce7300GT Kubuntu Edgy