From: Ryan Pavlik <rpav@users.sourceforge.net>
To: ruby-core@ruby-lang.org
Subject: Re: _id2ref bug? (another break)
Date: Fri, 15 Aug 2003 11:37:42 +0900 [thread overview]
Message-ID: <20030814193740.3a5948e1.rpav@users.sf.net> (raw)
In-Reply-To: <1060906889.631559.29136.nullmailer@picachu.netlab.jp>
On Fri, 15 Aug 2003 09:21:39 +0900
matz@ruby-lang.org (Yukihiro Matsumoto) wrote:
> Hi,
>
> In message "Re: _id2ref bug? (REPRODUCED, short)"
> on 03/08/15, Ryan Pavlik <rpav@users.sf.net> writes:
>
> |I was wrong, here's a short example that reproduces the problem exactly.
>
> Thank you. This is what I need. The following patch should fix the
> problem.
>
> matz.
Thanks... fixes my example great. Unfortunately it's still a problem in
the full code, but maybe this will help. In gc.c right above the patch:
printf("id2ref - %d, %d\n", BUILTIN_TYPE(ptr), RBASIC(ptr)->klass);
When running:
id2ref - 63, 135382017
/usr/local/encap/mephle-0.8.0/share/mephle/Driver/Storage_cache.rb:36:
[BUG] Segmentation fault
All of the others result in "2, <something>" or "0, <something>".
--
Ryan Pavlik <rpav@users.sf.net>
"I distinctly remember dancing on your grave." - 8BT
next prev parent reply other threads:[~2003-08-15 2:32 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 ` Ryan Pavlik [this message]
2003-08-15 3:35 ` _id2ref bug? (another break) 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
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=20030814193740.3a5948e1.rpav@users.sf.net \
--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).