[#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@...>
[email protected] 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
[#85616] Re: Why require autoconf 2.67+
— Vít Ondruch <v.ondruch@...>
2018/02/18
VGhpcyBjb3VsZCBoZWxwIHlvdSB0byBidWlsZCBSdWJ5IHdpdGggb2xkZXIgYXV0b2NvbmYgKDIu
[#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
[email protected] 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:85451] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults
From:
Vladimir Makarov <vmakarov@...>
Date:
2018-02-06 14:55:00 UTC
List:
ruby-core #85451
On 02/06/2018 05:00 AM, Eric Wong wrote: > Eric Wong <[email protected]> wrote: >> [email protected] wrote: >>> https://bugs.ruby-lang.org/issues/14357 >>> >>> The thread_safe gem is not maintained anymore, but I don't see >>> any reason why its test suite should segfault with Ruby 2.5. >> Right, no 3rd-party C exts loaded and I hit this in trunk, too. >> Using -fsanitize=address reveals use-after-free in st.c >> Investigating, but maybe Vladimir can find it sooner. > Maybe my initial investigation was correct, after all. > > valgrind takes forever, but indicates the free is caused by > rebuild_table; so it doesn't look like we missed GC marking > during rebuild. Disabling the free(tab->entries) at line > st.c:792 (patch below) seems to indicate success with the > thread_safe test suite (letting it loop overnight). > > Looks like the new_tab != tab case of rebuild is leaving a > hanging reference somewhere. > > Looks like it's freshly rebuilt table. Pretty easy to reproduce > the problem on 2.5, I remember it took more tries on 2.4 (didn't > valgrind). An extra pair of eyes more experienced with this > code than I am would be appreciated. Thanks. Eric, thank you for working on the problem and analyzing it. I'll look at this and try to fix it as soon as possible. Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>