From: nobu@...
Date: 2015-08-10T16:29:01+00:00
Subject: [ruby-core:70311] [Ruby trunk - Bug #11418] spawn segfaults

Issue #11418 has been updated by Nobuyoshi Nakada.


Because,
> Until 2.2, this has not appeared since `Process.spawn` didn't use `ALLOCV_N`.

Other methods storing `VALUE`s in `ALLOCV`ed buffers may cause segfaults.

----------------------------------------
Bug #11418: spawn segfaults
https://bugs.ruby-lang.org/issues/11418#change-53733

* Author: Nobuyoshi Nakada
* Status: Closed
* Priority: Normal
* Assignee: 
* ruby -v: 
* Backport: 2.0.0: REQUIRED, 2.1: REQUIRED, 2.2: REQUIRED
----------------------------------------
`Process.spawn` sometimes segfaults, because buffer allocated by `ALLOCV_N` is not marked, when the size exceeds 1024 bytes.
In these days, `TestEncodingConverter#test_default_external` has occasionally segfaulted by this problem.

Until 2.2, this has not appeared since `Process.spawn` didn't use `ALLOCV_N`.
Maybe unnecessary before 2.2.



-- 
https://bugs.ruby-lang.org/