Issue #13900 has been updated by naruse (Yui NARUSE).

Status changed from Open to Closed

As nobu wrote, this issue is already fixed.
You can avoid this by upgrading Ruby to 2.3.5 or 2.4.2.

----------------------------------------
Bug #13900: Segmentation fault - 2 different machines
https://bugs.ruby-lang.org/issues/13900#change-66687

* Author: marmotteNZ (pierre lonchampt)
* Status: Closed
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
The same error appears systematically - on two different installs of Ruby 2.3.1
A/ Ubuntu 16.04 in Windows10 WSL
B/ Bodhi 4.3.1    on a virtualBOx Windows 10 host.


I followed the message at the end inviting me to report a bug.   Hope it helps

```
BAcktrace:

peter@peter-VirtualBox:/media/sf_Dropbox_(Sonomat)/ENG/Code/Ruby$ ruby listSpectro.rb

listSpectro.rb:35: [BUG] Segmentation fault at 0x0000000000001c
(snip)
Aborted
peter@peter-VirtualBox:/media/sf_Dropbox_(Sonomat)/ENG/Code/Ruby$
```


---Files--------------------------------
bug-13900.log (26 KB)


-- 
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>