yes, thanks also for quickness

It means that reverting to a previous version of zlib and libxml2 (which would "work"), is not going to happen because

1) the older zlib is not secure

2) the changes zlib made that exposed the problems in libxml2 were valid changes for them to make

So it will not be fixed by reverting zlib.

Upstream says that things "are working" elsewhere and suggests that higuita's machine is somehow broken. That's possible, and it's also possible that something in Slackware is causing the breakage. I see that a libxul.so in a $HOME directory is part of the trace, so there's some stuff we don't ship at least involved with the code path (whether it matters or not).

Nobody has ever given me a reproducer on the supposed libxml2/zlib breakage...

2 members found this post helpful.

Ardour now builds against new lxml2 (although it's stll crash-prone). Fast fix, Pat.

Sooo... we can't revert, and upstream insists it's not broken. That kinda sucks.

As for reproducability, it seems I'm not the only one having a prob with Ardour in Slackware64 -current and 13.1.

FYI, I just built fine ardour from SBo on 64-current (pure, on multilib fails).

choqok and fwbuilder now compiles without error

Yeah, I can build it after Pat's fix... but it's still crash-prone.

For reproducing the ardour bug (which is 64 exclusive), under libxml2-2.7.7 and zlib-1.2.5 it's as simple as attempting to open any session. Ardour uses libxml to read in their session files (uncompressed), which then fails using the gzdirect() call from zlib on a test to see whether or not the file it is reading is compressed. Segfault, every time. Steps to reproduce:

Run ardour. Start a new Session. Save. Quit. Run ardour again. Open your session. Segfault.

I had put a backtrace in the other thread that specifically references this bug that 2handband had created.

Ardour insists it is not their problem (fairly true), libxml2 says the same as Pat mentions, and zlib folks are the ones who patched libxml2 to use this call. If Gentoo's bug report is accurate, they have some issue with their 64 bit implementation.

I have yet to test whether the new libxml2-2.7.8 package resolves, but I did grok the source, and the offending line is still in place. I think it's up to zlib to fix.

FYI, I rebuilt zlib with this two patches (the second should be the one needed, also archlinux applies that)

http://sources.gentoo.org/cgi-bin/vi...-ldflags.patch
http://sources.gentoo.org/cgi-bin/vi...fs-decls.patch

and ardour doesn't segfault anymore \o/

now I look around a little to see if I borked my install

Let us know!

Try the new update in -Current

Kick ass. Unfortunately I can't test immediately; the wife's going to be using this computer for the next couple of hours and she's a lot less philosophical about breakdowns than I am! I'll run the upgrade as soon as she's done.

I just got the new update installed, and now it turns out I've gotta run out of town for a few days. Damn. Will report back by Sunday.

can confirm that with zlib in testing ardour works fine

2 members found this post helpful.

Turned out I didn't have to leave after all. Got the new zlib installed, Ardour is WORKING!!! So far no breakages, will report anything weird. Pat, you're the man.