Mike Hommey wrote:
PS: You galeon crash with the unstable version is unrelated.
Are you sure? Why? Galeon did't segfault for me on quit before the
latest upgrade (sure, Galeon itself or any of it's other dependencies
could also have been upgraded).
Take a look at the backtrace, it doesn't involve libxml2.
Yes sure. And that segfault happened with the *non*-problematic libxml2
version. I should have been a little more clear: my whole point there
was that *another* change than the one in libxml2 might have introduced
a problem, which is just exhibited by the new libxml2. As we don't know
whether it's libxml2's fault or the fault of another library, I have to
mention every other breakage, too.
Now you may be right and it's not "related" to libxml2 in the sense that
libxml2 might not be at fault for those issues, *but* those segfaults
might be very well related in the sense that they might lead us to the
very same cause leading to the segfaults we see inside libxml2. So your
conclusion to not further look at those crashes can't be definitive
(with our current knowledge).
Christian.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
