[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

Python 2.7 is no longer supported.

--
nosy: +serhiy.storchaka
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[Chris Hogan]

Chris Hogan added the comment:

The Intel compiler team is looking into this issue.  I'll keep everyone updated 
here.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[Zachary Ware]

Zachary Ware added the comment:

This one is officially weird.

I can reliably reproduce the segfault in test_ascii_formatd on OSX with ICC 15 
or 16, using the included libffi in Modules/_ctypes/libffi_osx.  There are also 
segfaults in test_ctypes, test_multiprocessing, and test_threading (all 
stemming from an issue in ctypes).

Using libffi from Homebrew and --with-system-ffi, all the segfaults go away, 
and in fact all tests pass (with --with-icc from #25827, which adds '-fp-model 
strict' to CFLAGS).  The bundled 'nearly vanilla' libffi doesn't work with OSX; 
it doesn't make it through configure.

Somehow, argcount in _ctypes_callproc is being corrupted, but applying this 
patch somehow makes test_ascii_formatd pass:

diff -r 937774aa1853 Modules/_ctypes/callproc.c
--- a/Modules/_ctypes/callproc.cMon Dec 14 03:41:59 2015 +
+++ b/Modules/_ctypes/callproc.cFri Dec 18 02:10:04 2015 -0600
@@ -1168,6 +1168,7 @@
 PyErr_NoMemory();
 goto cleanup;
 }
+printf("line 1171, argcount %zd", argcount);
 for (i = 0; i < argcount; ++i) {
 atypes[i] = args[i].ffi_type;
 if (atypes[i]->type == FFI_TYPE_STRUCT)


I have absolutely no idea why that should work.  Adding that line before the 
previous statement still results in segfault, and adding it anywhere after line 
1178 also still results in segfault.  Even with the magic patch, test_ctypes 
still segfaults elsewhere.  I'm out of my depth as to what could be causing 
this or how to further diagnose it.

As a workaround, would it be kosher to mandate --with-system-ffi on Darwin when 
CC=icc?  As I recall, the custom libffi is necessary for regular OSX builds to 
accommodate fat binaries; how concerned are we about supporting fat binaries 
with ICC?

--
components: +ctypes

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[Chris Hogan]

Changes by Chris Hogan :


--
resolution: not a bug -> 
status: closed -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[R. David Murray]

R. David Murray added the comment:

We've figured out that the difference is the optimization level.  Without 
--with-pydebug, I can reproduce the failure.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[R. David Murray]

R. David Murray added the comment:

Someone can correct me if I'm wrong, but my expectation would be that since we 
use ICC for the main compile on the ICC buildbots, we also compile the bundled 
ctypes using it.  It is hard to see how any of the other modules would affect 
this.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[Chris Hogan]

Chris Hogan added the comment:

I guess since no one can reproduce the error, it must be a problem with how I'm 
building it.  We build our own dependencies (zlib, bzip, sqlite3, openssl, 
etc.) with the Intel compiler, so it could be any number of things causing the 
issue. Closing as not a bug.

--
resolution:  -> not a bug
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[STINNER Victor]

STINNER Victor added the comment:

See also issue #24999 about ICC compiler.

--
nosy: +haypo

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[Chris Hogan]

New submission from Chris Hogan:

I successfully built Python on OS X 10.10 with the Intel compiler v15.  
However, running the regression tests gives me a "segmentation fault: 11" on 
test_ascii_formated.  I think this has to do with libffi, because when I build 
with the --use-system-ffi flag (using a libffi that I built) all the regression 
tests pass, but I get a seg fault when I try to import ctypes.  Using python's 
libffi I can import ctypes, but I get seg faults in the tests.  Looking at 
libffi's homepage, it looks like x86-64 Mac OS X isn't on the list of 
officially supported platforms.  I tried contacting the libffi-discuss mailing 
list about this but have received no response in a month.  Please let me know 
what other information I can provide.

--
components: Macintosh, Tests
messages: 254398
nosy: christopher.hogan, ned.deily, ronaldoussoren
priority: normal
severity: normal
status: open
title: test_ascii_formatd fails on Mac when built with Intel compiler
type: crash
versions: Python 2.7, Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[Zachary Ware]

Zachary Ware added the comment:

Also, I haven't had an issue with this on my own machine.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[Zachary Ware]

Zachary Ware added the comment:

This doesn't seem to be a problem on the ICC buildbot; David, did you do 
anything special for libffi/ctypes?

--
nosy: +r.david.murray, zach.ware

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[Ned Deily]

Ned Deily added the comment:

Chris, how exactly are you running this test that fails and where does the test 
come from?  I may be overlooking something but I do not see any spelling of a 
test_ascii_formatted in the Python 3.5 source including its embedded ctypes.  
The ctypes shipped with Python certainly is supported on 64-bit OS X.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

[Chris Hogan]

Chris Hogan added the comment:

Ned, the test is in Lib/test/test_ascii_formatd.py.  Sorry, I spelled it wrong 
originally.  Also, I guess it's only in 2.7.  My mistake.

--
versions:  -Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com