[#1491] bug — Mathieu Bouchard <matju@...>
6 messages
2003/09/01
[#1492] non-blocking mode behavior (Re: bug)
— nobu.nokada@...
2003/09/01
Hi,
[#1512] New tests — Dave Thomas <Dave@...>
I was looking through the new test/ruby/* stuff just now, and notices
6 messages
2003/09/05
[#1533] GC disable / enable question — Torsten Rueger <torsten.rueger@...>
Moi,
7 messages
2003/09/17
[#1534] Re: GC disable / enable question
— nobu.nokada@...
2003/09/17
Hi,
[#1541] How to debug ? — Torsten Rueger <torsten.rueger@...>
Moi,
6 messages
2003/09/19
[#1542] Re: How to debug ?
— ts <decoux@...>
2003/09/19
>>>>> "T" == Torsten Rueger <torsten.rueger@hiit.fi> writes:
[#1551] Hashes as keys — "Nathaniel Talbott" <nathaniel@...>
I was just playing around with Hash#hash and discovered that you can't use a
13 messages
2003/09/23
[#1552] Re: Hashes as keys
— Jim Freeze <jim@...>
2003/09/23
On Wednesday, 24 September 2003 at 6:21:33 +0900, Nathaniel Talbott wrote:
[#1556] ostruct.rb patch — "Nathaniel Talbott" <nathaniel@...>
I've been finding OpenStruct to be very useful lately, and then I discovered
9 messages
2003/09/24
[#1557] Re: ostruct.rb patch
— "NAKAMURA, Hiroshi" <nahi@...>
2003/09/24
Hi, Nathaniel,
Re: How to debug ?
From:
Torsten Rueger <torsten.rueger@...>
Date:
2003-09-19 12:13:39 UTC
List:
ruby-core #1545
> It take me a few seconds to write an extension which crash ruby : now > I > can send you a "pure" ruby stack trace and ask you to debug my > extension > without giving the source. Can you do it ? You must be right, I am on the wrong list. This is not helpful at all. It crashed in rb_intern, I should have though that's robust, or you'd be interested in getting it robust (I mean it's ok to raise an exception but ruby shouldn't really crash in it's own) But if you're ok with this approach that you could write something to crash ruby in a few seconds extension coding, fine by me. I'll sign off soon. > You don't give enough information : the problem is perhaps in your > extension and nobody can know whith the information that you give. I had posted a link. purple.rubyforge.org . > One rule is to first search the bug in your extension, before trying > to look in ruby. Thank you. Yes I did that. Extensively. I have lots of test code, in fact that's how I found this bug. (And please remember, I wasn't asking you to fix it) So my two questions remain open: How can I debug such a problem: I mean how do I even find out what all thise eveal and funcalls do ? Is there some debug switch, so I can recompile ruby and it checks (asserts) all its assumptions about input to the functions? Along those lines. (I understand if noone wants to answer this after these comments) But the other: Is there anyone here that can create a new list? (Because ruby-talk is way too full and general) Thanks Torsten