I am sorry but I am unable to reduce this to a simpler test case, anyway I have put some minimal code that reproduces the issue in a gist with the error reports attached.
The box is a mecbook pro running snow leopard,
$ uname -a
Darwin mecbucpro.local 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64 x86_64
ruby comes from rvm and gcc -v says
Using built-in specs.
Configured with: /var/tmp/gcc/gcc-5666.3~123/src/configure --disable-checking --enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin10 --program-prefix=i686-apple-darwin10- --host=x86_64-apple-darwin10 --target=i686-apple-darwin10 --with-gxx-include-dir=/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Apple Inc. build 5666) (dot 3)
Let me know if I can help diagnose in some way.
Thanks for asking this question! However, without more information,
Team Nokogiri cannot reproduce your issue, and so we cannot offer much
Please provide us with:
A self-contained script (one that we can run without modification,
and preferably without making external network connections).
Please note that you need to include the XML/HTML that you are
The output of nokogiri -v, which will provide details about your
platform and versions of ruby, libxml2 and nokogiri.
For more information about requesting help or reporting bugs, please
take a look at http://bit.ly/nokohelp
Thank you so much!
I'm sorry isn't the code in the gist self contained enough? (it's at the end of the gist)
Or possibly you replied to the email, I accidentally hit "post" without adding the gist url, which I added in an edit of the original issue, and you may not have seen it.
nokogiri -v on my 1.9.2 setup is
# Nokogiri (1.5.2)
description: ruby 1.9.2p318 (2012-02-14 revision 34678) [x86_64-darwin10.8.0]
on 1.9.3 it's
# Nokogiri (1.5.2)
description: ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-darwin10.8.0]
Sorry for not posting to the list first, I did not do my homework in checking how to report and assumed github's issues were the right way :)
This doesn't repro in the latest version, so I think it can be closed now.
@zenspider thanks, closing.