https://bugs.kde.org/show_bug.cgi?id=412929
--- Comment #2 from Sam Saffron <sam.saff...@gmail.com> ---
Yeah I think usability wise the best thing would be:
```
gem install heaptrack_ruby
# in the ruby script
require 'heaptrack_ruby'
```
Then heaptrack can publish some sort of library to register callbacks for
scripting languages, and the ruby gem can then on require simply register the
"lookup frame function" in the heaptrack library.
Then you would use libunwind to get your stack followed by calling the callback
which is injected via ruby.
The actual code the Ruby extension would call to get the frame is along the
lines of:
```
if (ruby_thread_has_gvl_p() && ruby_current_vm_ptr &&
ruby_current_execution_context_ptr) {
int line;
const char *ptr = rb_source_location_cstr(&line);
}
```
So I guess the signature of the method would be something like this if my C is
write which it is likely not:
```
heaptrack_register_backtrace_lookup( *(char**)(void) )
```
--
You are receiving this mail because:
You are watching all bug changes.
