[OS] OS trunk segfaults on Mac during tests?

[Tony Kelman]

Ted gave me access to his machine which was very nice of him, but Macs are 
apparently not the easiest things to do debugging remotely. Odd permissions 
and code signing restrictions, it seems you need to give specific 
authentication every time you start a debugger, which wasn't working over 
SSH.

Anyway, turns out the problem is sort-of simple, but unexpected that it 
would cause a segfault and only on OSX. The file testMatricesAndCones.osil 
has 11 entries in the <cones> section, but it is labeled as 
numberOfCones="10." Apparently the <cones> parser needs a little bit more 
validation / consistency checking? Something must currently be triggering 
some undefined behavior that happens to get lucky with gcc, but segfaults 
with clang.

-Tony


-----Original Message----- 
From: Ted Ralphs
Sent: Sunday, February 08, 2015 8:33 PM
To: Tony Kelman
Cc: OS at list.coin-or.org
Subject: Re: OS trunk segfaults on Mac during tests?


Hi Tony,

Yes, I'm running builds at BatLab on OS X 7-10, but I haven't yet run unit 
tests on all those platforms. I do have a Mac sitting right in front of me, 
though, that I'd be happy to give you an account on if you want. I'll see if 
I can reproduce the problem, but won't have time to debug for a few days.

Cheers,

Ted


On Sun, Feb 8, 2015 at 11:06 PM, Tony Kelman <kelman at berkeley.edu> wrote:
Hi, this is a little tough for me to debug since I don't own a Mac myself, 
but on Travis CI I am seeing builds of OS trunk are segfaulting during "TEST 
7: Test parsing another OSiL file (testMatricesAndCones.osil)," at the step 
"Write the OSInstance object to a temporary file (i.e., string)."

The script that I'm running is the following:
svn co --non-interactive --trust-server-cert 
https://projects.coin-or.org/svn/OS/trunk OS-trunk
cd OS-trunk
for i in ASL Blas Lapack Metis Mumps; do cd ThirdParty/$i && ./get.$i && cd 
../../; done
./configure
make -j3
make -j3 -C OS/test alltests

The output log is at 
https://s3.amazonaws.com/archive.travis-ci.org/jobs/50010082/log.txt

Though since I don't have an interactive login to the test machine it's 
tough to get a full backtrace. I'll try configuring with --enable-debug to 
see if that gives any more useful output.

Ted, can you reproduce this? You sent me some info about batlab, but there 
you're also doing non-interactive batch jobs, right? You can't exactly run 
things interactively in a debugger there, can you?

-Tony






-- 

Dr. Ted Ralphs
Professor, Lehigh University
(610) 628-1280
ted 'at' lehigh 'dot' edu
coral.ie.lehigh.edu/~ted