[#88925] [Ruby trunk Feature#15095] [PATCH] share VM stack between threads and fibers if identical — ko1@...
Issue #15095 has been updated by ko1 (Koichi Sasada).
4 messages
2018/09/09
[#88927] Re: [Ruby trunk Feature#15095] [PATCH] share VM stack between threads and fibers if identical
— Eric Wong <normalperson@...>
2018/09/09
ko1@atdot.net wrote:
[#88926] [Ruby trunk Feature#15095] [PATCH] share VM stack between threads and fibers if identical — ko1@...
Issue #15095 has been updated by ko1 (Koichi Sasada).
3 messages
2018/09/09
[#89218] [Ruby trunk Bug#15130] open-uri hangs on cygwin — duerst@...
SXNzdWUgIzE1MTMwIGhhcyBiZWVuIHVwZGF0ZWQgYnkgZHVlcnN0IChNYXJ0aW4gRMO8cnN0KS4K
5 messages
2018/09/30
[ruby-core:89058] [Ruby trunk Bug#15116] Fixing issues detected by an Analysis tool.
From:
jaruga@...
Date:
2018-09-18 08:34:24 UTC
List:
ruby-core #89058
Issue #15116 has been updated by jaruga (Jun Aruga). Thank you for clarifying it! By the way, I saw your commit for the fix. https://github.com/ruby/ruby/commit/eddd630 ``` - close(slave); + if (slave < 0 && slave > 2) (void)!close(slave); ``` It seems that the `close` is never executed. That is `if (slave < 0 || slave > 2) (void)!close(slave);`, isn't it? ---------------------------------------- Bug #15116: Fixing issues detected by an Analysis tool. https://bugs.ruby-lang.org/issues/15116#change-74082 * Author: jaruga (Jun Aruga) * Status: Closed * Priority: Normal * Assignee: * Target version: * ruby -v: * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- When running a code analysis tool including several sub tools (mainly Coverty [1]), some issues were detected by it. You can refer attached issues_report.txt for detail. Some issues in the issues_report.txt might be false positive. (Those might be wrongly detected.) I tried to fix those by below 2 pull-requests. https://github.com/ruby/ruby/pull/1956 https://github.com/ruby/net-telnet/pull/15 The summary is * Fix leaked storage in addr2line.c. * Fix passing freed pointer as an argument in gc.c. * Fix leaked handle variable "n" in process.c. * Fix for "top_root" leaking the resource. After above patches, the issues were not detected. But I need your help to check if my code is valid. Thank you. [1] https://scan.coverity.com/ ---Files-------------------------------- issues_report.txt (7.74 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>