[#85349] [Ruby trunk Bug#14334] Segmentation fault after running rspec (ruby/2.5.0/erb.rb:885 / simplecov/source_file.rb:85) — pragtob@...
Issue #14334 has been updated by PragTob (Tobias Pfeiffer).
3 messages
2018/02/02
[#85358] Re: [ruby-cvs:69220] nobu:r62039 (trunk): compile.c: unnecessary freezing — Eric Wong <normalperson@...>
nobu@ruby-lang.org wrote:
5 messages
2018/02/03
[#85612] Why require autoconf 2.67+ — leam hall <leamhall@...>
Please pardon the intrusion; I am new to Ruby and like to pull the
6 messages
2018/02/17
[#85634] [Ruby trunk Bug#14494] [PATCH] tool/m4/ruby_replace_type.m4 use AC_CHECK_TYPES for HAVE_* macros — normalperson@...
Issue #14494 has been reported by normalperson (Eric Wong).
3 messages
2018/02/19
[#85674] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — matz@...
Issue #13618 has been updated by matz (Yukihiro Matsumoto).
5 messages
2018/02/20
[#85686] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/02/20
matz@ruby-lang.org wrote:
[#85704] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Koichi Sasada <ko1@...>
2018/02/21
On 2018/02/20 18:06, Eric Wong wrote:
[ruby-core:85762] Re: [Ruby trunk Bug#14542] syswrite spuriously empties the given string
From:
Eric Wong <normalperson@...>
Date:
2018-02-22 22:54:08 UTC
List:
ruby-core #85762
sylvain.joyeux@m4x.org wrote: > https://bugs.ruby-lang.org/issues/14542 > > * Target version: > * ruby -v: 2.3.6, 2.4.3 Hitting this in 2.4.3 might be my fault, but I'm not sure about Ruby 2.3.6 since my garbage reduction fixes aren't in that. For 2.4.3, can you try removing the rb_str_tmp_frozen_release call in the rb_io_syswrite function in io.c? > I'm doing a bit of buffer management to write on a socket. The main method looks like this: > > ~~~ ruby > @write_buffer.concat(new_bytes) if new_bytes > written_bytes = io.syswrite(@write_buffer) > @write_buffer = @write_buffer[written_bytes..-1] > !@write_buffer.empty? > ~~~ Just to cover all bases, are you somehow sharing @write_buffer between multiple threads? Or do you have any signal handler where @write_buffer may be clobbered? I'll try to be around this weekend to do some deeper investigation. Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>