On 2010-11-10, at 00:45, Daniel Veillard wrote: On Tue, Nov 09, 2010 at 02:50:23PM -0800, Mark Rowe wrote:
On 2010-11-09, at 07:37, Daniel Veillard wrote:
On Tue, Nov 09, 2010 at 04:01:02AM -0800, Mark Rowe wrote:
Based on your description it sounds like you've overwritten your
system copy of libxml2 with a copy that you built yourself from source.
Replacing system components of Mac OS X in this manner is not supported.
It's likely that the version of libxml2 you've installed is incompatible
with the Mac OS X system frameworks in some way which is leading to
the crashes that you're seeing.
Of course that got me curious. Do you have any specific patches
which could lead to such errors if not embedded in ? Except a change
in the way encoding are provided I don't really how such an error
could happen. Not that I suggest replacing system libraries, but
I wonder if you have patches which should be upstreamed,
The only substantial change from upstream libxml2 is the use of ICU
for encoding conversions rather than iconv. It's unlikely that this
Okay, I commited this and it's in 2.7.8 so that should not need further patch in the future (well except it's off by default it's a build setting).
That's good news! is related to the crash that James was seeing. The most likely cause
for this crash, based on previous experiences, would be a system library
relying on libxml2 internals, necessitating that the framework be rebuilt
when the version of libxml2 it is running against is changed.
Well libxml2 exposes most of its internals in the API, and I try very hard to not break those, so that's still a bit surprizing to me, it may happen bt I think we got hit only twice for the last decade or so in the Linux world (and people override default libs all the time :-)
I'm merely speculating as to the cause. I've not reproduced the problem myself nor have I looked particularly closely at the crash log. Crashes in unsupported configurations aren't something that I am personally going to spend much time on :-)
- Mark
|
