> C sure is lovely, isn't it. I will try to reproduce this. If you would
> not mind, please post this as a bug so I can track it at:
>
> http://rubyforge.org/tracker/?atid=1971&group_id=494&func=browse
Done -
http://rubyforge.org/tracker/index.php?func=detail&aid=17885&group_id=494&atid=1971
Wer
C sure is lovely, isn't it. I will try to reproduce this. If you would
not mind, please post this as a bug so I can track it at:
http://rubyforge.org/tracker/?atid=1971&group_id=494&func=browse
Dan
On Feb 7, 2008, at 03:36, Saurabh Nanda wrote:
>> Are you sure it is the doc reference and not
> Are you sure it is the doc reference and not the GC finalizers
> running? Put a print statement after it and see what happens.
Probably what you're saying is right. I don't fully understand what
effect the GC finalizers have, but I've tried the following script
(same script without the doc refer
Are you sure it is the doc reference and not the GC finalizers
running? Put a print statement after it and see what happens.
Dan
On Feb 6, 2008, at 17:11, Saurabh Nanda wrote:
> Why does the following code always cause a segfault on the last
> statement, when simply trying to refer to 'doc'? T
Why does the following code always cause a segfault on the last
statement, when simply trying to refer to 'doc'? The answer to this
could probably give me some pointers to my previous queries.
require 'xml/libxml'
x=XML::Parser.string("something")
doc=x.parse
x.parse
puts '-- about to print refer
