From: "ivoanjo (Ivo Anjo) via ruby-core" <ruby-core@...>
Date: 2023-05-12T23:24:11+00:00
Subject: [ruby-core:113463] [Ruby master Feature#10602] Support multithreaded profiling

Issue #10602 has been updated by ivoanjo (Ivo Anjo).


PR to implement this being discussed in https://github.com/ruby/ruby/pull/7784

----------------------------------------
Feature #10602: Support multithreaded profiling
https://bugs.ruby-lang.org/issues/10602#change-103042

* Author: mperham (Mike Perham)
* Status: Open
* Priority: Normal
----------------------------------------
The current `rb_profile_frames` captures the frame for whatever thread is current.  This makes profiling a multithreaded system impossible.  I'd like a `rb_thread_profile_frames` which captures a given thread.  It seems like it would be a very simple change, something like this:

~~~
int
rb_profile_frames(int start, int limit, VALUE *buff, int *lines)
{
    rb_profile_frames(start, limit, buff, lines, GET_THREAD())
}

int
rb_thread_profile_frames(int start, int limit, VALUE *buff, int *lines, rb_thread_t *th)
{
    int i;
    rb_control_frame_t *cfp = th->cfp, *end_cfp = RUBY_VM_END_CONTROL_FRAME(th);
    ...
~~~

This way profiling gems could lock to a specific thread.



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/