[#69084] [Ruby trunk - Feature #11124] [Open] [PATCH] lib/*: use monotonic clock for timeouts — normalperson@...
Issue #11124 has been reported by Eric Wong.
5 messages
2015/05/06
[#69138] [Ruby trunk - Feature #11136] [PATCH] webrick: avoid fcntl module — nobu@...
Issue #11136 has been updated by Nobuyoshi Nakada.
3 messages
2015/05/12
[#69160] [Ruby trunk - Feature #11146] [PATCH] variable.c: initialize generic_iv_tbl at start — nobu@...
Issue #11146 has been updated by Nobuyoshi Nakada.
4 messages
2015/05/13
[#69175] Re: [Ruby trunk - Feature #11146] [PATCH] variable.c: initialize generic_iv_tbl at start
— Eric Wong <normalperson@...>
2015/05/13
nobu@ruby-lang.org wrote:
[ruby-core:69130] [Ruby trunk - Feature #10932] Enabling allocation tracing as early as possible
From:
tenderlove@...
Date:
2015-05-12 00:12:36 UTC
List:
ruby-core #69130
Issue #10932 has been updated by 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? ---------------------------------------- Feature #10932: Enabling allocation tracing as early as possible https://bugs.ruby-lang.org/issues/10932#change-52381 * Author: Aaron Patterson * Status: Open * Priority: Normal * Assignee: Koichi Sasada ---------------------------------------- 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? ---Files-------------------------------- trace_start.diff (305 Bytes) -- https://bugs.ruby-lang.org/