Project

General

Profile

Actions
Copy link

Bug #13900

closed

Segmentation fault - 2 different machines

Bug #13900: Segmentation fault - 2 different machines

Added by marmotteNZ (pierre lonchampt) about 8 years ago. Updated about 8 years ago.

Status:
Closed
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
[ruby-core:82804]

Description

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) bug-13900.log nobu (Nobuyoshi Nakada), 09/15/2017 04:54 AM

Related issues 1 (0 open — 1 closed)

Is duplicate of Ruby - Bug #12670: Segmentation fault on `Magick::Image#get_pixels` on ruby since ruby-2.2Closedko1 (Koichi Sasada)Actions

Updated by naruse (Yui NARUSE) about 8 years ago Actions
Copy link
 #3 [ruby-core:82808]

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

Actions
Copy link

Also available in: PDF Atom