ruby-core

So, is it correct to assume that for language constructs that create built-in types like Range, Array, Hash etc that user-defined initialize methods are never called?

[#11549] Re: Proc initialize method not called under certain circumstances — "Berger, Daniel" <Daniel.Berger@...> 2007/06/28

> -----Original Message-----

[#11550] Re: Proc initialize method not called under certain circumstances — MenTaLguY <mental@...> 2007/06/28

On Fri, 29 Jun 2007 06:24:48 +0900, "John Lam (CLR)" <jflam@microsoft.com> wrote:

[#11553] Re: Proc initialize method not called under certain circumstances — "Marcel Molina Jr." <marcel@...> 2007/06/28

On Fri, Jun 29, 2007 at 06:54:49AM +0900, MenTaLguY wrote:

[#11554] Re: Proc initialize method not called under certain circumstances — murphy <murphy@...> 2007/06/28

> ... for language constructs that create

[#11560] Re: Proc initialize method not called under certain circumstances — Yukihiro Matsumoto <matz@...> 2007/06/29

Hi,

[#11548] NilClass, TrueClass, FalseClass special cased for singleton classes? — "John Lam (CLR)" <jflam@...>

If you do:

3 messages 2007/06/28

[#11557] Re: NilClass, TrueClass, FalseClass special cased for singleton classes? — Nobuyoshi Nakada <nobu@...> 2007/06/29

Hi,

[#11559] Re: NilClass, TrueClass, FalseClass special cased for singleton classes? — Joel VanderWerf <vjoel@...> 2007/06/29

John Lam (CLR) wrote:

[#11555] Name of Classes — =?ISO-8859-15?Q?Wolfgang_N=E1dasi-Donner?= <wonado@...>

Moin, moin!

2 messages 2007/06/28

[#11558] Re: Name of Classes — Nobuyoshi Nakada <nobu@...> 2007/06/29

Moin,

[#11556] delete_if with destructive methods in block — Florian Gross <florgro@...>

Hi,

3 messages 2007/06/29

[#11561] Re: [BUG] delete_if with destructive methods in block — Nobuyoshi Nakada <nobu@...> 2007/06/29

Hi,

[#11567] Re: delete_if with destructive methods in block — Florian Gross <florgro@...> 2007/06/30

That fixes it for me. I got no regressions from Rubinius' hash spec

[#11562] Can clear frozen array using initialize() — Florian Gross <florgro@...>

Hi,

2 messages 2007/06/29

[#11563] Re: [BUG] Can clear frozen array using initialize() — Yukihiro Matsumoto <matz@...> 2007/06/30

Hi,

Re: $2000 USD Reward for help fixing Segmentation Fault in GC

From: Ruben Vandeginste <snowbender@...>

Date: 2007-06-03 08:45:09 UTC

List: ruby-core #11397

Brent, Sylvain,

I don't think that valgrind is all that useful for this kind of
problem.  Valgrind will likely spew out a whole lot of warnings or
errors of the type "read from uninitialised memory location".  The
reason is the conservative garbage collector.  A conservative
collector scans all allocated memory (heap/stacks/..) searching for
values that look like pointers.  This includes memory that has been
allocated, but has not been written to yet.  In the context of a
program, one generally (unless reading out external input which is
mapped in memory for example) does not want to read from uninitialized
memory locations and in that case it is likely a bug in the program.
In the context of a conservative collector, reading from uninitialized
memory is part of the way a conservative collector works, and is
correct behaviour.  If the segmentation fault is actually coming from
a bug in the collector, valgrind won't be useful, or at least not
effective for tracking the bug down.  It's been a while since last
time I used valgrind, but if I remember correctly, a suppression file
will let you for example ignore the so-called 'errors' valgrind
detects in the collector code, but then you also won't find the
problematic code in the collector.... if that's where the bug is, of
course.  Valgrind is a really nice and really good tool, but not
useful for tracking down bugs in a (conservative) collector.

Kind regards,
Ruben

At Sun, 3 Jun 2007 01:31:43 +0900,
Brent Roman wrote:
> 
> Sylvain,
> 
> I plan to try valgrind on a ruby interpreter built for the x86 with all compiler 
> optimization disabled next week.  I'd never heard of valgrind before.
> 
> Note that ggarra@advancedsl.com.ar suggested this off-list a few
> days before you did.
> 
> It does sound promising.  
> 
> I'm hopeful that it might lead us to the cause of what appears
> to be a wild VAULE pointer write.
> 
> - brent
>  
> 
> 
> > If you can run your application on x86 and still have the crash, run the 
> > interpreter under valgrind. You'll have to generate a suppression file 
> > beforehand though.
> > -- 
> > Sylvain
> 
> -- 
>  Brent Roman
>  Software Engineer                 Tel: 831 775 1808
>  425 Clinton St., Santa Cruz,      California, 95062
>  mailto:brent@mbari.org  http://www.mbari.org/~brent
> 
>

Thread

Prev Next

In This Thread

Prev Next