| Age | Commit message (Collapse) | Author |
|
LLVM made release/11.x branch. Its master is now version 12.
Notes:
Merged: https://github.com/ruby/ruby/pull/3405
|
|
|
|
* RUBY_DEBUG_LOG: Logging debug information mechanism
This feature provides a mechanism to store logging information
to a file, stderr or memory space with simple macros.
The following information will be stored.
* (1) __FILE__, __LINE__ in C
* (2) __FILE__, __LINE__ in Ruby
* (3) __func__ in C (message title)
* (4) given string with sprintf format
* (5) Thread number (if multiple threads are running)
This feature is enabled only USE_RUBY_DEBUG_LOG is enabled.
Release version should not enable it.
Running with the `RUBY_DEBUG_LOG` environment variable enables
this feature.
# logging into a file
RUBY_DEBUG_LOG=/path/to/file STDERR
# logging into STDERR
RUBY_DEBUG_LOG=stderr
# logging into memory space (check with a debugger)
# It will help if the timing is important.
RUBY_DEBUG_LOG=mem
RUBY_DEBUG_LOG_FILTER environment variable can specify the fileter string.
If "(3) __func__ in C (message title)" contains the specified string, the
infomation will be stored (example: RUBY_DEBUG_LOG_FILTER=str will enable
only on str related information).
In a MRI source code, you can use the following macros:
* RUBY_DEBUG_LOG(fmt, ...): Above (1) to (4) will be logged.
* RUBY_DEBUG_LOG2(file, line, fmt, ...):
Same as RUBY_DEBUG_LOG(), but (1) will be replaced with given file, line.
Notes:
Merged-By: ko1 <ko1@atdot.net>
|
|
|
|
|
|
Also install external libraries only, extract-gems does not work
unless base ruby is available.
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3197
|
|
To honor the environment variable, keep GITPULLOPTIONS unset by
default, and appended the option to VCSUP.
|
|
Fetched tags by `make up` are not used, in CI environments.
|
|
Only the last commit is used, unless creating the ChangeLog file.
|
|
And fixed typo in compilers.yml.
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3094
|
|
Split ruby.h
Notes:
Merged-By: shyouhei <shyouhei@ruby-lang.org>
|