search

bsuh / node_xslt

a simple XSLT addon for node
zlib License
71 stars 17 forks source link

xmlMallocBreakpoint reached on block 0 #4

Closed RobeeeJay closed 12 years ago

RobeeeJay commented 12 years ago

I'm getting the following very bizarre error whenever I run an XSL template on XML and the result is empty:

(nil) : Freed()

xmlMallocBreakpoint reached on block 0

It had my head scratching for quite some time!

Also is there anyway to stop errors from bringing down node?

TIA!

(P.S. Really appreciate your work on this library, it's the only way I've found to use XSL with nodejs! Was it hard to write? I'm getting quite tempted to try and impliment an XQuery module)

bsuh commented 12 years ago

For the "bringing down node" problem try updating to the latest in the npm registry. I'll look into the "empty result" bug.

No problem. Actually I'm pretty surprised/excited that other people find this useful :) Thanks for using it. It took a day or two to learn and write the plugin but it was fairly easy since it's just a wrapper around libxslt. I imagine wrapping a XQuery library wouldn't be too hard.

RobeeeJay commented 12 years ago

I'm running the latest from the npm registry (afaik anyway, it's as new as npm update allows!) and this error at any rate bombs it out. :/

And yes it's very very useful, without it I couldn't have moved my dev work to node as xslt is a core part of my web work. :)

xslt itself winds me up a bit though, hence why I'm exploring options with xquery. It looks a lot easier to use, I just need to be able to use it inside node. If it took you a day or two, then maybe I should just give it a go, since I know C/C++ pretty well. In fact you've inspired me to seriously think about it now.

bsuh commented 12 years ago

I had just updated the registry when I wrote that comment. You should be able to update to 0.1.2.

RobeeeJay commented 12 years ago

Oh so it is. :) Thanks!

RobeeeJay commented 12 years ago

Ooh actually another issue, to do with building. I'm not sure if this is specific to node 0.4+ or CentOS, but node_xslt.cc gets compiled to ./build/Release/node_xslt yet it's referenced in package.json as ./build/debug/node_xslt so you get an error unless you either rename the directory or edit the package.json file to correct the path.

bsuh commented 12 years ago

Hi. Sorry for the wait. I have pushed a commit that I believe fixes both unresolved issues. If you could test the latest version from npm, that'd be great, because I was unable to reproduce the "xmlMallocBreakpoint reached on block 0".

RobeeeJay commented 12 years ago

I forgot how I reproduced this error, and despite trying I can't manage it now. So it's probably fixed, thanks very much!