Calvin,
If you can produce a test case then I can find the problem.
XML::Document.file is just
a pass through for XML::Parser.
Dan
On Sep 23, 2007, at 17:18, Calvin Bascom wrote:
> Dan,
>
> I am only working with libxml through the TAP class. It is a
> single XML
> document being parsed w
Dan,
I am only working with libxml through the TAP class. It is a single XML
document being parsed with a moderate number of accesses to that
document. All of the SEGV do have the garbage_collect line at
approximately the same spot.
I started putting what I am doing together as a test case t
Calvin,
This may have nothing to do with the latest code changes. There are
still plenty of features that have not been fixed (like I just did
for xpath). The parser class is one. I looked at the _xpath_context
code and there does not appear to be much of an opportunity for
corruption ther
Dan,
This one occurs even less frequently than the last one, but
unfortunately it still segfaults occasionally when garbage collection
kicks in. It appears to crop up in random places (inside active-record,
inside erb, etc.) instead of just when the XML document access is
occurring like the p
Calvin,
This bug took some time to find, but I got it. XPath was probably the
best way to expose it, since it had to do with random access to nodes
(really freeing them, but what's the difference). It would have had
an impact somewhere else for sure.
It is all committed and an update should
Dan,
The TAP code I pasted in the original email is fine to use for a test
case. As far as the XML document, let me create a smaller version of
the one you currently have with the stuff I don't need ripped out of it
and send that to you in place of the current XML document you have so
the res
Calvin,
The change in stack trace was helpful (never imagined I would say
that, since they are usually worthless). I looked at how xpath.find
was handling its arguments and there was something, well, not quite
right. I reworked it and ran your case with this code:
IO.popen("gzcat rwtest/tap
I have just committed a re-write of XPath/XPointer and *.find (calls
to XPath). It is svn
revision 183. See if it fixes this problem.
Note, there is an incompatibility, the new XPath::Object class does
not support .xpath method, but I could find no reason to carry it
forward.
If it works, I
Hi,
As you suspected, this is the same problem. Your report helps to
confirm my
suspicions. It is the memory handing inside the xpath/node_set
portion of
the extension. I think I have figured out how to solve the problem,
now I just
need an hour to do it. Please bear with me, this is the top
I'm using the XML::Parser to parse XML data passed in as a string. The
parse works fine and my code then goes on to access elements and
attributes in the resulting document. If I use this code outside of the
Ruby on Rails environment, I never have any segfaults and everything
works as expecte
10 matches
Mail list logo
