Feature #10932: Enabling allocation tracing as early as possible

• Status: Assigned
• Assignee: ko1 (Koichi Sasada)
• Target version: -

[tenderlovemaking (Aaron Patterson)]

Hi,

I'd like to be able to enable allocation tracing as early as possible. I've attached a patch that I use to do that when I'm debugging code that I don't know very well.

The way I use it is like this:

$ ruby -robjspace/trace_start some_test.rb

I like using this because many times I can't figure out when to enable object tracing. Can we add this feature to object space?

[ko1 (Koichi Sasada)]

Matz has no objection (except file name).

I have 2 concerns.

(1) file name

We alraedy have tracer.rb.

How about objspace/allocation_tracer.rb?
(not clear?)

(2) including ObjectSpace

Should not include.

[tenderlovemaking (Aaron Patterson)]

How about objspace/allocation_tracer.rb?

I think that is fine.

Should not include.

Any reason why not? Usually I don't know where to include it while I'm debugging, and doing ObjectSpace.allocation_sourcefile is a lot to type. If including isn't an option, could we add shorter method names?

[ko1 (Koichi Sasada)]

Aaron Patterson wrote:

Should not include.

Any reason why not? Usually I don't know where to include it while I'm debugging, and doing ObjectSpace.allocation_sourcefile is a lot to type. If including isn't an option, could we add shorter method names?

I'm not sure we can restrict usage only to debugging.

[mame (Yusuke Endoh)]

• Related to Feature #17762: A simple way to trace object allocation added

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Assigned