[#79914] [Ruby trunk Bug#13282] opt_str_freeze does not always dedupe — normalperson@...
Issue #13282 has been reported by Eric Wong.
4 messages
2017/03/05
[#80140] [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus) — shyouhei@...
Issue #13295 has been updated by shyouhei (Shyouhei Urabe).
5 messages
2017/03/13
[#80362] Re: [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus)
— Eric Wong <normalperson@...>
2017/03/26
shyouhei@ruby-lang.org wrote:
[#80368] Re: [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus)
— SASADA Koichi <ko1@...>
2017/03/27
On 2017/03/26 15:16, Eric Wong wrote:
[#80205] Re: [ruby-cvs:65166] duerst:r58000 (trunk): clarifiy 'codepoint' in documentation of String#each_codepoint — Eric Wong <normalperson@...>
duerst@ruby-lang.org wrote:
4 messages
2017/03/17
[#80213] Re: [ruby-cvs:65166] duerst:r58000 (trunk): clarifiy 'codepoint' in documentation of String#each_codepoint
— Martin J. Dürst <duerst@...>
2017/03/17
Hello Eric,
[#80290] [Ruby trunk Feature#13355] [PATCH] compile.c: optimize literal String range in case/when dispatch — normalperson@...
Issue #13355 has been reported by normalperson (Eric Wong).
4 messages
2017/03/23
[#80410] Re: [Ruby trunk Feature#13355] [PATCH] compile.c: optimize literal String range in case/when dispatch
— Eric Wong <normalperson@...>
2017/03/27
normalperson@yhbt.net wrote:
[#80415] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
5 messages
2017/03/28
[#80488] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
4 messages
2017/03/29
[ruby-core:79975] [Ruby trunk Bug#13258] Segmentation fault at 0x00000000000000 during instance_eval
From:
dr.drax@...
Date:
2017-03-09 03:33:57 UTC
List:
ruby-core #79975
Issue #13258 has been updated by David Drakard. What appears to be the same problem also occurs when running inside Puma. ---------------------------------------- Bug #13258: Segmentation fault at 0x00000000000000 during instance_eval https://bugs.ruby-lang.org/issues/13258#change-63398 * 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>