Segment fault when make test, with node v0.2.6

[Joson]

Hi,
I'd installed libxmljs successful, but got a segment fault when
made test:

os: debian
node : v0.2.6
libxmljs: v0.4.1. (downloaded yesterday)


# make node
... ...
scons: done building targets.

# make test
node --expose_gc spec/tacular.js
EEEEEEEEEmake: *** [test] Segmentation fault

# make test-verbose
node --expose_gc spec/tacular.js --verbose
spec_xml_parse_errors.js
Parse error object
has a domain accessor :
has a code accessor :
has a level accessor :
has a file accessor :
has a line accessor :
has a str1 accessor :
has a str2 accessor :
has a str3 accessor :
has a int1 accessor :
has a column accessor :

spec_text_node.js
Text node
knows its type is "text" :
knows its name is "text" :

Comment node
knows its type is "comment" :
knows its name is "comment" :

CDATA node
knows its type is "cdata" :
has no name :

spec_searching.js
Finding a node
can be done with #get : Error (AssertionError: == {"document":{}})
can be done with #find : Error (AssertionError: 4 == 2)
can be nested : Error (TypeError: Cannot call method 'get' of
undefined)

Finding a non-prefix namespaced node
can be done with #get : Error (AssertionError: == {"document":{}})
can be done with #find : Error (AssertionError: 4 == 2)
can be nested : Error (TypeError: Cannot call method 'get' of
undefined)

Finding a prefixed namespaced node
can be done with #get : Error (AssertionError: == {"document":{}})
can be done with #find : Error (AssertionError: 4 == 2)
can be nested : Error (TypeError: Cannot call method 'get' of
undefined)

spec_ref_integrity.js
Referential Integrity
doesn't crash :
Keeps references :

spec_attribute.js
Attribute
can be created without a namespace : make: *** [test-verbose]
Segmentation fault

Is there version incompatibility? If so, which version of libxmljs is
running on nodejs-0.2.6?
Thanks in advanced.

Joson

[Marco Rogers]

It's not likely that this is a version problem. The current version on npm has worked since node 0.2.something. What you're seeing is a test that is failing that tracks a bug that needs to be fixed. It only happens when there is a GC at a critical point. Which is something I wanted to make very explicit in the tests. Are you running into this in your code? If so, could you open a ticket on github and post your problem.

If you're *not* running into this, but just concerned about the test failing, I would tentatively tell you not to worry about it for now. Go ahead and use libxmljs as you normally would. These referential integrity issues are part of a larger overhaul that I'm planning. Unfortunately there is no eta right now. I'm in the middle of several other things. As always, patches are welcome.

Thanks

:Marco