Bug #13317: Console Segmentation fault at 0x00000000000038

• Status: Third Party's Issue
• Assignee: -
• Target version: -
• ruby -v: ruby 2.3.3p222 (2016-11-21 revision 56859) [x86_64-darwin16]
• Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN

[erowlin (Thomas Romera)]

First: It's been 3 years I'm daily using Ruby, and that's the first time I encounter such a bug, so, thank you for all the hard work. That's awesome.
Here is the bug report :

I don't have much to add, was querying my DB with AR. (I redacted some sensible parts)

[nobu (Nobuyoshi Nakada)]

• File bug-13317.log bug-13317.log added
• Description updated (diff)
• Status changed from Open to Third Party's Issue

2   ruby                                0x000000010bd2a4e4 sigsegv + 68
3   libsystem_platform.dylib            0x00007fff97cacbba _sigtramp + 26
4   ruby                                0x000000010bda1c28 method_entry_get + 72
5   ruby                                0x000000010bda1d4b rb_callable_method_entry + 27
6   ruby                                0x000000010bdb71d0 rb_call0 + 48
7   ruby                                0x000000010bda5916 rb_funcall + 374
8   byebug.bundle                       0x000000010d0f809f is_living_thread + 63
9   byebug.bundle                       0x000000010d0f82cb release_lock + 123
10  byebug.bundle                       0x000000010d0f687d raw_return_event + 157
11  ruby                                0x000000010bdbf81e exec_hooks_protected + 222
12  ruby                                0x000000010bdbd2b5 rb_threadptr_exec_event_hooks_orig + 357

It happens just in byebug extension.
Please report it to byebug.