Feature #2260: better access with GC_DEBUG

• Status: Rejected
• Assignee: -
• Target version: -

[rogerdpack (Roger Pack)]

=begin
It would be nice to be able to know where [what line of code] objects were allocated one.

For instance
ObjectSpace.each_object{|o| puts o.debug_info }

or something like

a = 'b'
ObjectSpace.describe(a)
=> "instance of String at 0xffff from line 4 file irb"

Then users could use it to more easily search for memory reference leaks.

Since the information is already there with the "-DGC_DEBUG=1" flag, it should be possible.
I'd be happy to give it a shot if it would be useful.

Thoughts?
-r
=end

[matz (Yukihiro Matsumoto)]

=begin
Hi,

In message "Re: [ruby-core:26262] [Feature #2260] better access with GC_DEBUG"
on Sat, 24 Oct 2009 06:31:44 +0900, Roger Pack [e-mail] writes:

|It would be nice to be able to know where [what line of code] objects were allocated one.

|Since the information is already there with the "-DGC_DEBUG=1" flag, it should be possible.
|I'd be happy to give it a shot if it would be useful.
|
|Thoughts?

But most compilation is done without GC_DEBUG turned on. I am not
positive about the method that only available on specific compilation
condition.

						matz.

=end

[rogerdpack (Roger Pack)]

• Status changed from Open to Rejected

=begin
too obscure, apparently, to be useful.
=end