From: "ko1 (Koichi Sasada)" Date: 2013-11-27T11:59:49+09:00 Subject: [ruby-core:58619] [ruby-trunk - Feature #9162][Rejected] Read/Write operations in Tracepoint Issue #9162 has been updated by ko1 (Koichi Sasada). Status changed from Assigned to Rejected > Is there a way to access when variables are read/assigned in Tracepoint? No. I reject this approach because of performance (without enabling these trace). But there is no proof of my assumption. Please try and measure. > Or should I use some other approach? I planned dynamic instrumentation. But there is still C-extension problem. ---------------------------------------- Feature #9162: Read/Write operations in Tracepoint https://bugs.ruby-lang.org/issues/9162#change-43188 Author: davidann (David Weiser) Status: Rejected Priority: Normal Assignee: ko1 (Koichi Sasada) Category: core Target version: Is there a way to access when variables are read/assigned in Tracepoint? Specifically, I'm interested in creating a tool which does dynamic, threading analysis of Ruby code to find atomicity violations, dead-locks and race conditions. However, to do so would require the ability to know when a variable is written to, or read from, and the thread in which the operation happened. I looked in vm_trace.c and did not find the events that would be needed to do this type of analysis. Can I use Tracepoint to get this information? Or should I use some other approach? -- http://bugs.ruby-lang.org/