Bug#874727: closed by Anton Gladky (Bug#874727: fixed in coin3 3.1.4~abc9f50+dfsg2-1)
I've attached an xml tool table. * start FreeCAD from the command line * Create a new document * switch to "Path" Workbench * start "Path Manager" from the Path menu * import attached tooltable (note the file type selection) You'll get: Program received signal SIGSEGV, Segmentation fault. #0 /lib/x86_64-linux-gnu/libc.so.6(+0x35fc0) [0x7f75fc00ffc0] #1 /lib/x86_64-linux-gnu/libexpat.so.1(XML_SetHashSalt+0x1b) [0x7f75f584095b] #2 /usr/lib/python2.7/lib-dynload/pyexpat.x86_64-linux-gnu.so(+0x75b0) [0x7f75c08145b0] #3 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x94d6) [0x7f7602316c66] #4 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x8e5f) [0x7f76023165ef] #5 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x8e5f) [0x7f76023165ef] #6 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x732) [0x7f760230d032] I don't think the file itself matters at all because it segfaults while trying to initialise libexpat, but in case the attachment gets filtered, this is the content: On Fri, 5 Oct 2018 10:03:26 +0200 Christoph Berg wrote: > Re: markus 2018-10-05 <20181004193807.40af399c@yolanda> > > it's a packaging bug - libcoin is statically linked with libexpat, > > and the version being used is outdated. So anything that uses > > libcoin and libexpat will run into a segfault. > > > > I am not aware of any other application that uses libcoin. > > I noticed because PostGIS is affected via postgis B-D -> libsfcgal-dev > -> libsfcgal-osg1 -> libopenscenegraph100v5 -> libcoin80v5. Looking > at https://udd.debian.org/cgi-bin/autoremovals.cgi there's quite a few > packages depending on coin3. So the question whether this affects > freecad only or more packages is making quite a difference. > > Do you have a recipe on how to reproduce the bug with freecad from > experimental? > > Christoph tt.xml Description: XML document
Bug#874727: closed by Anton Gladky <gl...@debian.org> (Bug#874727: fixed in coin3 3.1.4~abc9f50+dfsg2-1)
Version libcoin89-dev 3.1.4-abc9f50+dfsg3-2 (in Debian Testing as of yesterday) still has a statically linked version of libexpat - and still causes any application using the system version libexpat to segfault. 3.1.4-abc9f50+dfsg2-1 never became available in Testing - not sure what happened. On Thu, 21 Dec 2017 12:21:09 + "Debian Bug Tracking System"wrote: > This is an automatic notification regarding your Bug report > which was filed against the libcoin80v5 package: > > #874727: libcoin80v5: Program using libcoin80v5 and any other library > that uses lebexpat1 segfaults. > > It has been closed by Anton Gladky . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Anton Gladky > by replying to this email. > >
Bug#874727: libcoin80v5: Program using libcoin80v5 and any other library that uses lebexpat1 segfaults.
Hi, it breaks FreeCAD, the current version in Debian testing (0.16) and the next version (0.17) which is currently under development. Steps to reproduce in FreeCAD 0.16: * open new file * create a box (or some other part) * switch to Path workbench and create a project * edit tool table * if you don't already have a tool table xml file add a tool and "Export" the tool table * "Import" the tool table -> segfault HTH, Markus On Sat, 9 Sep 2017 22:11:47 +0200 Anton Gladkywrote: > tags 874727 +moreinfo > severity 874727 important > thanks > > Hi, > > thank you for the bugreport. Please provide some more information, > what packages in Debian are affected. > > Thanks > > Anton > > > 2017-09-09 11:33 GMT+02:00 markus : > > Package: libcoin80v5 > > Version: 3.1.4~abc9f50+dfsg1-2 > > Severity: critical > > Justification: breaks unrelated software > > > > Dear Maintainer, > > > > Due to the change in libexpat1 (since 2.2.0, currently at 2.2.3) > > the included copy of it in libcoin results in segfaults of any > > program that uses libexpat1. Specifically any program that uses xml > > from python and links against libcoin will segfault. > > > > The stacktrace looks like it is a problem with libexpat1 leading to > > a segfault in XML_SetHashSalt - however looking at that function > > there is no way it could possibly segfault - unless of course the > > provided XMLParser pointer does not actually point to what expat > > expects to be an XMLParser - which is indeed the case because the > > XMLParser instance was created by a call into lobcoin which is > > still on libexpat 2.2.0.