https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112015-04-08T10:12:05ZRuby Issue Tracking SystemRuby master - Feature #10932: Enabling allocation tracing as early as possiblehttps://bugs.ruby-lang.org/issues/10932?journal_id=520732015-04-08T10:12:05Zko1 (Koichi Sasada)
<ul></ul><p>Matz has no objection (except file name).</p>
<p>I have 2 concerns.</p>
<p>(1) file name</p>
<p>We alraedy have tracer.rb.</p>
<p>How about objspace/allocation_tracer.rb?<br>
(not clear?)</p>
<p>(2) including ObjectSpace</p>
<p>Should not include.</p> Ruby master - Feature #10932: Enabling allocation tracing as early as possiblehttps://bugs.ruby-lang.org/issues/10932?journal_id=523812015-05-12T00:12:35Ztenderlovemaking (Aaron Patterson)tenderlove@ruby-lang.org
<ul></ul><blockquote>
<p>How about objspace/allocation_tracer.rb?</p>
</blockquote>
<p>I think that is fine.</p>
<blockquote>
<p>Should not include.</p>
</blockquote>
<p>Any reason why not? Usually I don't know where to include it while I'm debugging, and doing <code>ObjectSpace.allocation_sourcefile</code> is a lot to type. If including isn't an option, could we add shorter method names?</p> Ruby master - Feature #10932: Enabling allocation tracing as early as possiblehttps://bugs.ruby-lang.org/issues/10932?journal_id=528992015-06-13T07:54:02Zko1 (Koichi Sasada)
<ul></ul><p>Aaron Patterson wrote:</p>
<blockquote>
<blockquote>
<p>Should not include.</p>
</blockquote>
<p>Any reason why not? Usually I don't know where to include it while I'm debugging, and doing <code>ObjectSpace.allocation_sourcefile</code> is a lot to type. If including isn't an option, could we add shorter method names?</p>
</blockquote>
<p>I'm not sure we can restrict usage only to debugging.</p> Ruby master - Feature #10932: Enabling allocation tracing as early as possiblehttps://bugs.ruby-lang.org/issues/10932?journal_id=911842021-03-30T23:48:25Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/17762">Feature #17762</a>: A simple way to trace object allocation</i> added</li></ul>