[#85940] [Ruby trunk Bug#14578] Forking a child process inside of a mutex crashes the ruby interpreter — ben.govero@...
Issue #14578 has been reported by bengovero (Ben Govero).
3 messages
2018/03/05
[#86205] [Ruby trunk Feature#14618] Add display width method to String for CLI — aycabta@...
Issue #14618 has been reported by aycabta (aycabta .).
3 messages
2018/03/19
[#86366] Re: [ruby-cvs:70102] usa:r63008 (trunk): get rid of test error/failure on Windows introduced at r62955 — Eric Wong <normalperson@...>
usa@ruby-lang.org wrote:
3 messages
2018/03/28
[ruby-core:85905] [Ruby trunk Bug#13895] TestVMDump test fails on High Sierra
From:
nagachika00@...
Date:
2018-03-03 02:39:53 UTC
List:
ruby-core #85905
Issue #13895 has been updated by nagachika (Tomoyuki Chikanaga).
Backport changed from 2.2: DONTNEED, 2.3: REQUIRED, 2.4: REQUIRED to 2.2: DONTNEED, 2.3: REQUIRED, 2.4: DONE
ruby_2_4 r62640 merged revision(s) 59893,59922.
----------------------------------------
Bug #13895: TestVMDump test fails on High Sierra
https://bugs.ruby-lang.org/issues/13895#change-70760
* Author: hsbt (Hiroshi SHIBATA)
* Status: Closed
* Priority: Normal
* Assignee:
* Target version: 2.5
* ruby -v: ruby 2.5.0dev (2017-09-14 trunk 59870) [x86_64-darwin17]
* Backport: 2.2: DONTNEED, 2.3: REQUIRED, 2.4: DONE
----------------------------------------
TestVMDump#test_darwin_invalid_call fails with `Timeout::Error`
I can reproduce with `ruby -rfiddle -e "Fiddle::Function.new(Fiddle::Pointer.new(1), [], Fiddle::TYPE_VOID).call"`.
After that backtrace was stopped "C level backtrace information" section. like this
```
~ > ruby -rfiddle -e "Fiddle::Function.new(Fiddle::Pointer.new(1), [], Fiddle::TYPE_VOID).call"
-e:1: [BUG] Segmentation fault at 0x0000000000000001
ruby 2.5.0dev (2017-09-14 trunk 59870) [x86_64-darwin17]
-- Crash Report log information --------------------------------------------
See Crash Report log file under the one of following:
* ~/Library/Logs/DiagnosticReports
* /Library/Logs/DiagnosticReports
for more details.
Don't forget to include the above Crash Report log file in bug reports.
-- Control frame information -----------------------------------------------
c:0003 p:---- s:0010 e:000009 CFUNC :call
c:0002 p:0041 s:0006 e:000005 EVAL -e:1 [FINISH]
c:0001 p:0000 s:0003 E:002150 (none) [FINISH]
-- Ruby level backtrace information ----------------------------------------
-e:1:in `<main>'
-e:1:in `call'
-- Machine register context ------------------------------------------------
rax: 0x0000000000000000 rbx: 0x00007ffee4ff8d88 rcx: 0x0000000000000000
rdx: 0x0000000000000000 rdi: 0x0000000000000000 rsi: 0x0000000000000000
rbp: 0x00007ffee4ff8c00 rsp: 0x00007ffee4ff8bf8 r8: 0x0000000000000000
r9: 0x0000000000000000 r10: 0x00007ffee4ff8b50 r11: 0x0000000000000001
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x000000010b1566e0
r15: 0x00007ffee4ff8d70 rip: 0x0000000000000001 rfl: 0x0000000000010246
-- C level backtrace information -------------------------------------------
(stopped this line)
```
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>