- From: lpsmith at spod-central.org (Lucian Smith)
- Subject: [cellml-dev] [libsbml-team] Changing state in libxml
- Date: Sat, 19 Feb 2011 00:40:20 +0000
And indeed, configuring lisbml with expat instead makes the problem go
away, as expected.
This is a reasonable workaround for now, but I would still like to find a
more permanent solution.
-Lucian
* Frank T. Bergmann <fbergman at caltech.edu> [2011-02-19 00:18] writes:
>
Perhaps you could try to configure libsbml to work with expat, or xerces-c.
>
That will help you to narrow down your suspicion. If the crash persists then
>
you know that it is not due to both libraries using libxml.
>
>
Cheers
>
Frank
>
>
> -----Original Message-----
>
> From: libsbml-team-bounces at caltech.edu [mailto:libsbml-team-
>
> bounces at caltech.edu] On Behalf Of Lucian Smith
>
> Sent: Friday, February 18, 2011 4:12 PM
>
> To: A list for the developers of CellML tools
>
> Cc: libSBML Team
>
> Subject: [libsbml-team] Changing state in libxml
>
>
>
> When trying to code up a translator which would convert between CellML,
>
> Antimony, and SBML, I ran into the following problem.
>
>
>
> Right now, I have libsbml configured to use libxml, the same XML parser
>
that
>
> CellML uses. I can read a document in with libsbml, and everything is
>
fine. I
>
> can then read a document with the CellML API, and everything is fine.
>
> However, if I then read that same document with libsbml, I get a segfault
>
> error, and if I run it though valgrind, I'm actually getting an invalid
>
read.
>
>
>
> Attached is a smallish program that demonstrates this issue. It seems to
>
me
>
> that CellML is changing the state of libxml in some way, and this messes
>
up the
>
> subsequent libsbml call, causing the segfault.
>
>
>
> So my question is: how does CellML change the state of libxml, and how do
>
I
>
> undo this? Or is there something else going on?
>
>
>
> -Lucian
>
>
Archive powered by MHonArc 2.6.18.