-
Notifications
You must be signed in to change notification settings - Fork 737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[2201.2.x] Add ability to get strand dump during code execution #36767
[2201.2.x] Add ability to get strand dump during code execution #36767
Conversation
Codecov Report
@@ Coverage Diff @@
## 2201.2.x #36767 +/- ##
==============================================
+ Coverage 74.36% 74.37% +0.01%
- Complexity 48916 48950 +34
==============================================
Files 3279 3280 +1
Lines 189394 189541 +147
Branches 24734 24744 +10
==============================================
+ Hits 140846 140979 +133
- Misses 40425 40434 +9
- Partials 8123 8128 +5
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Purpose
$title
Fixes #36210
Fixes #36733
Fixes #36284
Approach
Samples
To get the strand dump when a Ballerina program is running, the user needs to get the PID of the Ballerina program (possibly using jps) and then send the SIGTRAP signal to that process.
Eg:
kill -5 $PID
or
kill -s TRAP $PID
(Note: This feature is not supported in some operating systems (like Windows) where
TRAP
POSIX signal is not supported.)Some example strand dumps
Remarks
Check List