From: nobu.nokada@softhome.net
To: ruby-core@ruby-lang.org
Subject: Re: _id2ref bug? (another break)
Date: Sat, 16 Aug 2003 21:54:10 +0900 [thread overview]
Message-ID: <200308161254.h7GCs8PL018865@sharui.nakada.kanuma.tochigi.jp> (raw)
In-Reply-To: <200308161108.h7GB8cl23133@moulon.inra.fr>
Hi,
At Sat, 16 Aug 2003 20:08:44 +0900,
ts wrote:
> n> Ryan is correct.
>
> not for me. There is a difference between protecting ruby againt coredump
> and writing stupid code.
I agree that the protection should work.
> n> $ ruby -e 'x = ""; eval("x"); y = ""; x = [x.id, y.id]; x.min.step(x.max, 10){|i| p ObjectSpace._id2ref(i)}'
>
> I'll never trust a module which have such code, and I hope that *no*
> modules in the standard distribution do something like this.
I know nothing about his code, and this is pure ruby code. It
means that the protection doesn't work enough correctly now.
--
Nobu Nakada
prev parent reply other threads:[~2003-08-16 12:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 16:45 _id2ref bug? Ryan Pavlik
2003-08-14 16:57 ` Yukihiro Matsumoto
2003-08-14 17:01 ` ts
2003-08-14 17:08 ` Yukihiro Matsumoto
2003-08-14 17:44 ` Ryan Pavlik
2003-08-14 17:46 ` Ryan Pavlik
2003-08-15 0:10 ` Yukihiro Matsumoto
2003-08-14 18:09 ` _id2ref bug? (REPRODUCED, short) Ryan Pavlik
2003-08-15 0:21 ` Yukihiro Matsumoto
2003-08-15 2:37 ` _id2ref bug? (another break) Ryan Pavlik
2003-08-15 3:35 ` nobu.nokada
2003-08-15 4:19 ` Ryan Pavlik
2003-08-15 4:48 ` Ruby Tk on Mac OS X Mark Wilson
2003-08-15 5:22 ` nobu.nokada
2003-08-15 6:10 ` Mark Wilson
2003-08-15 7:14 ` nobu.nokada
2003-08-15 10:17 ` _id2ref bug? (another break) ts
2003-08-15 17:42 ` Ryan Pavlik
2003-08-16 9:35 ` ts
2003-08-16 11:02 ` nobu.nokada
2003-08-16 11:08 ` ts
2003-08-16 12:54 ` nobu.nokada [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200308161254.h7GCs8PL018865@sharui.nakada.kanuma.tochigi.jp \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).