[issue42309] BUILD: AIX-64-bit segmentation fault using xlc-v11

[Michael Felt]

Michael Felt  added the comment:

OK - looking at this again.

This looks very similiar to another 'coredump' issue (will have to look for the 
number later). iirc, when something called 'pgen', or similiar was modified.

Here is a lengthy `dbx` dump.

If I am reading this correctly, it is 'starting' in this area:

_PyPegen_run_parser(p = 0x0fffcb40), line 1121 in "pegen.c"
_PyPegen_run_parser_from_string(str = "compile", start_rule = 1, filename_ob = 
0x0001100ee2b0, flags = 0x0707fb30, arena = 0x070d3330), 
line 1250 in "pegen.c"
PyPegen_ASTFromStringObject(str = warning: Unable to access address 0x15d4 from 
core
(invalid char ptr (0x15d4)), filename = (nil), mode = 268435455, 
flags = 0x482448c2, arena = 0x0001001a1e3c), line 27 in "peg_api.c"
Py_CompileStringObject(str = "", filename = (nil), start = 268435455, flags = 
0x0707fb30, optimize = 268435455), line 1274 in "pythonrun.c"
builtin_compile_impl(module = 0x000100077a0c, source = (nil), filename = 
0x00011e28, mode = "", flags = 1, dont_inherit = 1, optimize = 0, 
feature_version = 0), line 819 in "bltinmodule.c"
builtin_compile(module = (nil), args = 0x0001100741c0, nargs = 2, kwnames = 
0x070068f0), line 274 in "bltinmodule.c.h"
cfunction_vectorcall_FASTCALL_KEYWORDS(func = 0x0fffd030, args = 
0x1300, nargsf = 0, kwnames = 0x0008), line 457 in 
"methodobject.c"


Here is the complete 'where' status:

(dbx) where
strncmp.strncmp(??, ??, ??) at 0x901b3a0
_get_keyword_or_name_type(p = 0x0020, name = (nil), name_len = 0), 
line 535 in "pegen.c"
_PyPegen_fill_token(p = 0x0001001be088), line 638 in "pegen.c"
_PyPegen_is_memoized(p = 0x0020, type = 0, pres = 
0x0fffc370), line 716 in "pegen.c"
dotted_name_rule(p = 0x0fffc400), line 3443 in "parse.c"
dotted_as_name_rule@AF452_298(??), line 3410 in "parse.c"
_gather_36_rule@AF453_127(??), line 17755 in "parse.c"
dotted_as_names_rule@AF454_299(??), line 3368 in "parse.c"
import_name_rule(p = 0x0fffc660), line 3000 in "parse.c"
import_stmt_rule@AF462_305(??), line 2932 in "parse.c"
small_stmt_rule(p = 0x0fffc7a0), line 1606 in "parse.c"
unnamed block in simple_stmt_rule(p = 0x0001000df758), line 1428 in 
"parse.c"
simple_stmt_rule(p = 0x0001000df758), line 1428 in "parse.c"
unnamed block in statement_rule(p = 0x15d5), line 1262 in "parse.c"
statement_rule(p = 0x15d5), line 1262 in "parse.c"
_loop1_11_rule(p = 0x0001000df6d4), line 16254 in "parse.c"
statements_rule@AF475_318(??), line 1197 in "parse.c"
file_rule@AF476_324(??), line 730 in "parse.c"
_PyPegen_run_parser(p = 0x0fffcb40), line 1121 in "pegen.c"
_PyPegen_run_parser_from_string(str = "compile", start_rule = 1, filename_ob = 
0x0001100ee2b0, flags = 0x0707fb30, arena = 0x070d3330), 
line 1250 in "pegen.c"
PyPegen_ASTFromStringObject(str = warning: Unable to access address 0x15d4 from 
core
(invalid char ptr (0x15d4)), filename = (nil), mode = 268435455, 
flags = 0x482448c2, arena = 0x0001001a1e3c), line 27 in "peg_api.c"
Py_CompileStringObject(str = "", filename = (nil), start = 268435455, flags = 
0x0707fb30, optimize = 268435455), line 1274 in "pythonrun.c"
builtin_compile_impl(module = 0x000100077a0c, source = (nil), filename = 
0x00011e28, mode = "", flags = 1, dont_inherit = 1, optimize = 0, 
feature_version = 0), line 819 in "bltinmodule.c"
builtin_compile(module = (nil), args = 0x0001100741c0, nargs = 2, kwnames = 
0x070068f0), line 274 in "bltinmodule.c.h"
cfunction_vectorcall_FASTCALL_KEYWORDS(func = 0x0fffd030, args = 
0x1300, nargsf = 0, kwnames = 0x0008), line 457 in 
"methodobject.c"
PyVectorcall_Call(callable = 0x0fffd0c0, tuple = 0x070b9900, 
kwargs = 0x070bf1c8), line 257 in "call.c"
do_call_core(tstate = 0x0001, func = 0x0002, callargs = 
0x0001, kwdict = 0x0001100741c0), line 5092 in "ceval.c"
_PyEval_EvalFrameDefault(tstate = 0x0fffd370, f = 0x070aced8, 
throwflag = 1), line 3580 in "ceval.c"
_PyEval_EvalCode(tstate = 0x9f63fdf1699118db, _co = 0x0704ed80, globals 
= 0x070754c0, locals = 0x07051070, args = 0x0fffd4a0, 
argcount = 4765972565237396600, kwnames = 0x0001000bb5e4, kwargs = 
0x070683b0, kwcount = 2, kwstep = 0, defs = (nil), defcount = 0, kwdefs 
= (nil), closure = (nil), name = 0x07055ad0, qualname = 
0x07055ad0), line 40 in "pycore_ceval.h"
_PyFunction_Vectorcall(func = 0x0fffd560, stack = 0x0001100aefa8, 
nargsf = 1152921504606836064, kwnames = 0x070b70f0), line 413 in 
"call.c"
_PyEval_EvalFrameDefault(tstate = 0x00010001c9c4, f = 0x000b99c0, 
throwflag = 268435455), line 621 in "abstract.h"
_PyEval_EvalCode(tsta

[issue42309] BUILD: AIX-64-bit segmentation fault using xlc-v11

[Michael Felt]

Michael Felt  added the comment:

For now, I am going to suggest closing this - as a bug in the xlc-v11 compiler 
- and not worth researching.

I am able to build the 3.9 distribution as well as the 3.10 master using the 
xlC-v13-1.3.2 (Try and Buy) version.

Thanks for thinking together!

--
title: BUILD: AIX-64-bit segmentation fault using xlc -> BUILD: AIX-64-bit 
segmentation fault using xlc-v11

___
Python tracker 

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

[issue42309] BUILD: AIX-64-bit segmentation fault using xlc

[Michael Felt]

Michael Felt  added the comment:

Added "using xlc" to description.

When I have a system that has 64-bit support for gcc - I'll verify that it 
works, or does not work, for me using gcc.

--
title: BUILD: AIX-64-bit segmentation fault -> BUILD: AIX-64-bit segmentation 
fault using xlc

___
Python tracker 

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

[issue42309] BUILD: AIX-64-bit segmentation fault

[Kevin]

Kevin  added the comment:

I have not encountered this problem when building Python 3.10 on AIX and PASE 
with GCC 6.3.

--
nosy: +kadler

___
Python tracker 

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

[issue42309] BUILD: AIX-64-bit segmentation fault

[Michael Felt]

Michael Felt  added the comment:

On a different server, different compiler (xlc-v13, mine is xlc-v11) it gets 
past this point.

So, perhaps it is a compiler issue.

As the second system is missing many 64-bit libraries - still cannot build 
64-bit Python-3.9.

Low priority - imho.

--

___
Python tracker 

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

[issue42309] BUILD: AIX-64-bit segmentation fault

[Michael Felt]

New submission from Michael Felt :

Successfully built and packaged the Python-3.9.0 distribution tar archive 
without modification - as 32-bit.

Repeating the same process with the following environment change:

 # export OBJECT_MODE=64

fails with a segmentation fault by the "first-phase" python executable:

```
../src/py39-3.9.0/Modules/makexp_aix Modules/python.exp "." 
libpython3.9.a
 xlc_r -Wl,-bE:Modules/python.exp -lld -o python Programs/python.o 
libpython3.9.a -lintl -ldl  -lm   -lm
 ./python -E -S -m sysconfig --generate-posix-vars ; if test $? -ne 0 ; 
then  echo "generate-posix-vars failed" ;  rm -f ./pybuilddir.txt ;  exit 1 ;  
fi
/bin/sh: 6291700 Segmentation fault(coredump)
make: 1254-004 The error code from the last command is 139.


Stop.
root@x066:[/data/prj/python/py39-3.9.0]./python -E -S -m sysconfig 
--generate-posix-vars
Segmentation fault(coredump)
root@x066:[/data/prj/python/py39-3.9.0]./python
Segmentation fault(coredump)
```

Will try to duplicate in a second environment.

--
components: Build
messages: 380654
nosy: Michael.Felt
priority: normal
severity: normal
status: open
title: BUILD: AIX-64-bit segmentation fault
type: crash
versions: Python 3.9

___
Python tracker 

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