[#8484] strptime fails to properly parse certain inputs — <noreply@...>

Bugs item #5263, was opened at 2006-08-01 23:14

13 messages 2006/08/02
[#8485] Re: [ ruby-Bugs-5263 ] strptime fails to properly parse certain inputs — Yukihiro Matsumoto <matz@...> 2006/08/02

Hi,

[#8538] Re: [ ruby-Bugs-5263 ] strptime fails to properly parse certain inputs — nobu@... 2006/08/06

Hi,

[#8561] sandbox timers & block scopes — why the lucky stiff <ruby-core@...>

Two puzzles I am trying to solve:

28 messages 2006/08/08
[#8624] Re: sandbox timers & block scopes — why the lucky stiff <ruby-core@...> 2006/08/15

raise ThisDecayingInquisition, "anyone? anyone at all?"

[#8627] Re: sandbox timers & block scopes — MenTaLguY <mental@...> 2006/08/15

On Wed, 2006-08-16 at 00:35 +0900, why the lucky stiff wrote:

[#8628] Re: sandbox timers & block scopes — why the lucky stiff <ruby-core@...> 2006/08/15

On Wed, Aug 16, 2006 at 02:46:30AM +0900, MenTaLguY wrote:

[#8629] Re: sandbox timers & block scopes — "Charles O Nutter" <headius@...> 2006/08/15

On 8/15/06, why the lucky stiff <ruby-core@whytheluckystiff.net> wrote:

[#8690] a ruby-core primer — why the lucky stiff <ruby-core@...>

Hello, all. I've been working on the ruby-core page for the new Ruby site.

21 messages 2006/08/22

cooperating with other GCs

From: MenTaLguY <mental@...>
Date: 2006-08-30 23:17:38 UTC
List: ruby-core #8759
Hello, I'm currently in the process of embedding a Ruby interpreter in a
C++ application which uses its own conservative garbage collector,
relying upon the ability to inspect the C stack.

Unfortunately, the stacks of Ruby threads other than the current one (as
well as stack snapshots saved as part of continuations) are not visible
to the collector, resulting in premature collections.

One solution would be to patch the allocation function(s) used for
allocating the stack snapshots, to notify the non-Ruby collector to
treat those memory ranges as roots.  However, it is not clear how to do
this without modifying the Ruby interpreter.

Another solution would be to patch ruby_xmalloc() etc. to use the
application GC's allocator, although that could cause problems with
excessive false pointers since all Ruby memory (including strings) would
be scanned.

Are there any other suggestions, or any solutions which don't involve a
patched Ruby interpreter?  I would like to be able to use the user's
installed Ruby interpreter if possible.

-mental

Attachments (1)

signature.asc (191 Bytes, application/pgp-signature)

In This Thread

Prev Next