[MacPorts] #34520: dia crashes on start

[MacPorts]

#34520: dia crashes on start
----------------------------------+-----------------------------------------
 Reporter:  luc_j_bourhis@…       |       Owner:  macports-tickets@…                   
     Type:  defect                |      Status:  new                                  
 Priority:  Normal                |   Milestone:                                       
Component:  ports                 |     Version:  2.1.1                                
 Keywords:                        |        Port:  dia                                  
----------------------------------+-----------------------------------------

Comment(by macports@…):

 0.97.2_1 also crashes on startup for me (creating a 350MB core file, if I
 let it; my backtrace looks identical to the one on the ticket), on OS X
 10.6.8.

 If I reactivate 0.97.2_0, and fudge a backwards compatibility symlink for
 a library that got upgraded since I built 0.97.2_0:

 {{{
 ewen at bethel:~$ dia FILE.dia
 dyld: Library not loaded: /opt/local/lib/libffi.5.dylib
   Referenced from: /opt/local/bin/dia
   Reason: image not found
 Trace/BPT trap
 ewen at bethel:~$
 }}}
 with
 {{{
 ewen at bethel:~$ cd /opt/local/lib
 ewen at bethel:/opt/local/lib$ sudo ln -s libffi.6.dylib libffi.5.dylib
 }}}
 then dia will start up and load my file.

 The difference between 0.97.2_0 and 0.97.2_1 is one changeset r90852, in
 response to ticket #33616, which adds in a forced use of a SVG library.
 Given the way it crashes (after a long time reading in lots of data) I
 wonder if the issue is that it's then trying to use the SVG library to
 load a non-SVG thing?

 The other possibility is that it has to do with environment at the built
 time (eg, compiler, etc).  But it looks like something is wrong with the
 argument to fread() and/or flockfile(), particularly since in trying to
 grab a stack trace I'm seeing the segmentation fault happen _before_ it
 appears to stat/open the first shape file (based on trying to use dtruss,
 but after it's read in the directory).  I guess the idea would be to try
 to rebuild _1 with that library disabled again, and see if it makes it
 work again.

-- 
Ticket URL: <https://trac.macports.org/ticket/34520#comment:11>
MacPorts <http://www.macports.org/>
Ports system for Mac OS