ruby.git/vm_dump.c, branch v3_2_11 The Ruby Programming Language Fix backtrace beyond _singtramp on macOS arm64 (#7015) 2022-12-23T17:24:55+00:00 NARUSE, Yui nurse@users.noreply.github.com 2022-12-23T17:24:55+00:00 ee60756495b775c4e8fc93a57094ac4e4b83fa7f * move ptrauth_strip logic into vm_dump.c * don't use _sigtramp special logic on arm64 
* move ptrauth_strip logic into vm_dump.c
* don't use _sigtramp special logic on arm64
 push dummy frame for loading process 2022-10-20T08:38:28+00:00 Koichi Sasada ko1@atdot.net 2022-10-17T08:50:42+00:00 e35c528d721d209ed8531b10b46c2ac725ea7bf5 This patch pushes dummy frames when loading code for the profiling purpose. The following methods push a dummy frame: * `Kernel#require` * `Kernel#load` * `RubyVM::InstructionSequence.compile_file` * `RubyVM::InstructionSequence.load_from_binary` https://bugs.ruby-lang.org/issues/18559 
This patch pushes dummy frames when loading code for the
profiling purpose.

The following methods push a dummy frame:
* `Kernel#require`
* `Kernel#load`
* `RubyVM::InstructionSequence.compile_file`
* `RubyVM::InstructionSequence.load_from_binary`

https://bugs.ruby-lang.org/issues/18559
Expand tabs [ci skip] 2022-07-21T16:42:04+00:00 Takashi Kokubun takashikkbn@gmail.com 2022-07-21T16:23:58+00:00 5b21e94bebed90180d8ff63dad03b8b948361089 [Misc #18891] 
[Misc #18891]
Prevent printing crash report in a loop 2022-06-03T17:50:32+00:00 Alan Wu XrXr@users.noreply.github.com 2022-03-29T17:38:55+00:00 e4fe3473027393aa084f4e6b2a01c29ec8281f99 In the event that we are crashing due to a corrupt Ruby stack, we might re-enter rb_vm_bugreport() due to failed assertions in rb_backtrace_print_as_bugreport() or SDR(). In these cases we were printing the bug report ad infinitum with unbounded recusion. I seem to run into this every once in a while and the amount of log it prints out is pretty distracting. On CI environments it makes the log output unnecessarily big. Let's fix this. 
In the event that we are crashing due to a corrupt Ruby stack, we might
re-enter rb_vm_bugreport() due to failed assertions in
rb_backtrace_print_as_bugreport() or SDR(). In these cases we were
printing the bug report ad infinitum with unbounded recusion.

I seem to run into this every once in a while and the amount of log it
prints out is pretty distracting. On CI environments it makes the log
output unnecessarily big. Let's fix this.
remove `NON_SCALAR_THREAD_ID` support 2022-05-24T01:06:51+00:00 Koichi Sasada ko1@atdot.net 2022-05-23T17:56:59+00:00 d9984f39d32f4cd692a35f4d803f7754ea262805 `NON_SCALAR_THREAD_ID` shows `pthread_t` is non-scalar (non-pointer) and only s390x is known platform. However, the supporting code is very complex and it is only used for deubg print information. So this patch removes the support of `NON_SCALAR_THREAD_ID` and make the code simple. 
`NON_SCALAR_THREAD_ID` shows `pthread_t` is non-scalar (non-pointer)
and only s390x is known platform. However, the supporting code is
very complex and it is only used for deubg print information.

So this patch removes the support of `NON_SCALAR_THREAD_ID`
and make the code simple.
introduce struct `rb_native_thread` 2022-04-22T18:08:27+00:00 Koichi Sasada ko1@atdot.net 2022-04-22T12:19:03+00:00 03d21a4fb099da7c52e6591e17704c297871b7db `rb_thread_t` contained `native_thread_data_t` to represent thread implementation dependent data. This patch separates them and rename it `rb_native_thread` and point it from `rb_thraed_t`. Now, 1 Ruby thread (`rb_thread_t`) has 1 native thread (`rb_native_thread`). 
`rb_thread_t` contained `native_thread_data_t` to represent
thread implementation dependent data. This patch separates
them and rename it `rb_native_thread` and point it from
`rb_thraed_t`.

Now, 1 Ruby thread (`rb_thread_t`) has 1 native thread (`rb_native_thread`).
Enable C backtraces on Apple silicon (#5770) 2022-04-20T02:52:47+00:00 Jean byroot Boussier jean.boussier+github@shopify.com 2022-04-20T02:52:47+00:00 fa2df520bcaaf3957db0489f1237311f091ac08d Co-authored-by: Jean Boussier <jean.boussier@gmail.com> 
Co-authored-by: Jean Boussier <jean.boussier@gmail.com>
 [DOC]Some link prefix replace 2022-04-09T08:43:46+00:00 S-H-GAMELINKS gamelinks007@gmail.com 2022-04-09T07:53:13+00:00 5b467400d220125aed9d000e258c3cc3ca505421 






Prefix ccan headers (#4568)
2022-03-30T07:36:31+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2022-03-30T07:36:31+00:00

42a0bed351979cb4a59c641fa5f03e49609561fd

* Prefixed ccan headers

* Remove unprefixed names in ccan/build_assert

* Remove unprefixed names in ccan/check_type

* Remove unprefixed names in ccan/container_of

* Remove unprefixed names in ccan/list

Co-authored-by: Samuel Williams <samuel.williams@oriontransfer.co.nz>




* Prefixed ccan headers

* Remove unprefixed names in ccan/build_assert

* Remove unprefixed names in ccan/check_type

* Remove unprefixed names in ccan/container_of

* Remove unprefixed names in ccan/list

Co-authored-by: Samuel Williams <samuel.williams@oriontransfer.co.nz>






Add ISEQ_BODY macro
2022-03-24T14:03:51+00:00

Peter Zhu
peter@peterzhu.ca

2022-03-23T19:19:48+00:00

5f10bd634fb6ae8f74a4ea730176233b0ca96954

Use ISEQ_BODY macro to get the rb_iseq_constant_body of the ISeq. Using
this macro will make it easier for us to change the allocation strategy
of rb_iseq_constant_body when using Variable Width Allocation.





Use ISEQ_BODY macro to get the rb_iseq_constant_body of the ISeq. Using
this macro will make it easier for us to change the allocation strategy
of rb_iseq_constant_body when using Variable Width Allocation.