Jeremy Evans

  • Email:
  • Registered on: 08/04/2010
  • Last connection: 03/13/2014

Activity

Reported issues: 31

03/13/2014

08:34 PM ruby-trunk Bug #9573: descendants of a module don't gain its future ancestors, but descendants of a class, do
First Last wrote:
> What is the objection to explaining how this works?
nobu explained how it works. However, as...

03/07/2014

04:18 AM ruby-trunk Bug #9606: Ocassional SIGSEGV inTestException#test_machine_stackoverflow on OpenBSD
Same result with the nightly snapshot.tar.gz (ruby -v: ruby 2.2.0dev (2014-03-07 trunk 45279) [x86_64-openbsd])
02:07 AM ruby-trunk Bug #9606: Ocassional SIGSEGV inTestException#test_machine_stackoverflow on OpenBSD
Unfortunately, I lost the original core dump, so this core dump is slightly different, but the basic problem is the s...

03/06/2014

10:24 PM ruby-trunk Bug #9606 (Feedback): Ocassional SIGSEGV inTestException#test_machine_stackoverflow on OpenBSD
ruby 2.1.1 on OpenBSD seems to occassionally suffer from a stack overflow when running TestException#test_machine_sta...

01/03/2014

01:38 PM ruby-trunk Bug #9351 (Closed): Make Rinda::RingFinger work correctly on OpenBSD and NetBSD
The current Rinda::RingFinger code assumes that the IP_MULTICAST_LOOP socket option takes int, but in NetBSD and Open...
01:32 PM ruby-trunk Bug #9350 (Closed): Handle IP_MULTICAST_LOOP and IP_MULTICAST_TTL socket options correctly on Ope...
OpenBSD is similar to NetBSD in that the IP_MULTICAST_LOOP and IP_MULTICAST_TTL socket options take unsigned char and...
08:37 AM ruby-trunk Bug #9348 (Closed): --with-tcllib and --with-tklib configure options not working correctly
When using the --with-tcllib=tcl85 -with-tklib=tk85 configure options, ruby still tries to use -ltcl -ltk as linker o...

12/23/2013

03:54 PM ruby-trunk Bug #9005: object.send(:define_method, ...){...} creates private method
There's only two days until the release of 2.1.0, and this still hasn't been fixed. This is a serious regression tha...

12/07/2013

01:22 AM ruby-trunk misc #8288: Ruby 2.1.0 release engeneering
I think #9005 and #9141 need to be fixed first, as they break existing code due to changes in method visibility.

12/02/2013

09:02 AM Backport93 Backport #9193 (Closed): ruby 1.9.3-p484 still vulnerable to CVE-2013-4287 and CVE-2013-4363 in i...
It appears that ruby 2.0.0-p353 included an update to rubygems 2.0.10 which fixes CVE-2013-4287 and CVE-2013-4363. ru...

Also available in: Atom