diff options
| author | Yusuke Endoh <mame@ruby-lang.org> | 2020-09-05 21:18:45 +0900 |
|---|---|---|
| committer | Yusuke Endoh <mame@ruby-lang.org> | 2020-09-06 13:57:41 +0900 |
| commit | 369cfabd5936ccb522f8e95e0f9cc65b59ea4039 (patch) | |
| tree | 81eea199cc4f0fa663d709056eebe1f4f1a139b5 /regcomp.c | |
| parent | c12b2703bc05f8c7eaaace49253f63a5e0f28273 (diff) | |
| download | ruby-369cfabd5936ccb522f8e95e0f9cc65b59ea4039.tar.gz | |
Make it possible to dump and load an exception object
A backtrace object in an exception had never supported marshalling
correctly: `Marshal.load(Marshal.dump(exc)).backtrace_locations` dumped
core.
An Exception object has two hidden instance varibles for backtrace data:
one is "bt", which has an Array of Strings, and the other is
"bt_locations", which has an Array of Thread::Backtrace::Locations.
However, Exception's dump outputs data so that the two variables are the
same Array of Strings. Thus, "bt_locations" had a wrong-type object.
For the compatibility, it is difficult to change the dump format. This
changeset fixes the issue by ignoring data for "bt_locations" at the
loading phase if "bt_locations" refers to the same object as "bt".
Future work: Exception's dump should output "bt_locations"
appropriately.
https://bugs.ruby-lang.org/issues/17150
Diffstat (limited to 'regcomp.c')
0 files changed, 0 insertions, 0 deletions