[#79440] [Ruby trunk Bug#13188] Reinitialize Ruby VM. — shyouhei@...
Issue #13188 has been updated by Shyouhei Urabe.
6 messages
2017/02/06
[#79441] Re: [Ruby trunk Bug#13188] Reinitialize Ruby VM.
— SASADA Koichi <ko1@...>
2017/02/06
On 2017/02/06 10:10, shyouhei@ruby-lang.org wrote:
[#79532] Immutable Strings vs Symbols — Daniel Ferreira <subtileos@...>
Hi,
15 messages
2017/02/15
[#79541] Re: Immutable Strings vs Symbols
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2017/02/15
Em 15-02-2017 05:05, Daniel Ferreira escreveu:
[#79543] Re: Immutable Strings vs Symbols
— Daniel Ferreira <subtileos@...>
2017/02/16
Hi Rodrigo,
[#79560] Re: Immutable Strings vs Symbols
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2017/02/16
Em 15-02-2017 22:39, Daniel Ferreira escreveu:
[ruby-core:79800] [Ruby trunk Bug#13258] Segmentation fault at 0x00000000000000 during instance_eval
From:
dr.drax@...
Date:
2017-02-27 13:27:44 UTC
List:
ruby-core #79800
Issue #13258 has been reported by David Drakard. ---------------------------------------- Bug #13258: Segmentation fault at 0x00000000000000 during instance_eval https://bugs.ruby-lang.org/issues/13258 * Author: David Drakard * Status: Open * 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 ---------------------------------------- My program is a website that runs inside webrick. Intermittently when calling instance_eval, a segmentation fault occurs, producing console output as shown in the attached file. I have not been able to spot a pattern to when the segmentation faults occur. My program dynamically (re)evaluates source code with every request. I am not sure, but the segmentation faults may occur after a source file is changed, although usually a change like this causes no problem, and when a segmentation fault has occurred, the server runs fine after restarting. For some reason I have only seen this problem so far in development, not in production. Because of the intermittent and seemingly random nature of the problem and the complexity of the code base, I have not been able to make a simple recreation, and I doubt I will be able to without some extra information. I am open to instrumenting my program to capture more information if I can get instructions to do so. Thank you for providing Ruby ---Files-------------------------------- console_error_out.txt (63.6 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>