libxml2 issue on 10.10 beta

[Michael Dickens]

> I will admit that I did not yet parse -all- of the files in the crash
> log yet to verify their linkage

I created a new file with just the binaries from the crash log, then:
{{{
% for tf in `cat crash_binaries_2.txt`; do fff="`otool -L $tf | grep
libxml2`"; if [ "${fff}" ]; then echo "${tf} : ${fff}"; fi; done
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/lxml/etree.so
:         /opt/local/lib/libxml2.2.dylib (compatibility version 12.0.0,
current version 12.1.0)
/opt/local/lib/libxslt.1.dylib :        /opt/local/lib/libxml2.2.dylib
(compatibility version 12.0.0, current version 12.1.0)
/opt/local/lib/libexslt.0.dylib :       /opt/local/lib/libxml2.2.dylib
(compatibility version 12.0.0, current version 12.1.0)
/opt/local/lib/libxml2.2.dylib : /opt/local/lib/libxml2.2.dylib:
        /opt/local/lib/libxml2.2.dylib (compatibility version 12.0.0,
        current version 12.1.0)
/System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
:    /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current
version 10.9.0)
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
:    /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current
version 10.9.0)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
:   /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current
version 10.9.0)
/usr/lib/libxar.1.dylib :       /usr/lib/libxml2.2.dylib (compatibility
version 10.0.0, current version 10.9.0)
/System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork :  
/usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version
10.9.0)
/System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation
:      /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current
version 10.9.0)
/System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore : 
       /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current
version 10.9.0)
/usr/lib/libxml2.2.dylib : /usr/lib/libxml2.2.dylib:
        /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current
        version 10.9.0)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation : 
       /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current
version 10.9.0)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
:         /usr/lib/libxml2.2.dylib (compatibility version 10.0.0,
current version 10.9.0)
/usr/lib/libarchive.2.dylib :   /usr/lib/libxml2.2.dylib (compatibility
version 10.0.0, current version 10.9.0)
/System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore
:        /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current
version 10.9.0)
/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit :        
/usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version
10.9.0)
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
:    /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current
version 10.9.0)
/usr/lib/libxslt.1.dylib :      /usr/lib/libxml2.2.dylib (compatibility
version 10.0.0, current version 10.9.0)
}}}

So ... it could be an indirect linkage between some MacPorts-provided
file, an Apple-provided system framework, and then Apple's
libxml2.2.dylib ... - MLD