[issue34355] SIGSEGV (Address boundary error)

2018-08-07 Thread Yohan Boniface 

New submission from Yohan Boniface :

Hi!

Just installed 3.7 (ArchLinux) and I've a SIGSEGV on one of my projects.
I've a hard time reducing to a minimal testcase, because it seems whatever 
random piece of code I remove the crash disappears at some point.

Here is the repository:

https://framagit.org/ybon/trefle

To reproduce, install the project in a 3.7 venv with `python setup.py develop` 
then run `python trefle/bin.py` (or even `python -c 'from trefle import 
routine'`).

Here is the output I have:

```
Initializing config
Done initializing config
fish: “python trefle/bin.py” terminated by signal SIGSEGV (Address boundary 
error)
```

Here are some elements:

- if I run the code with PYTHONMALLOC=debug, I have no crash
- the project is using quite a lot of unicode (French content written in config 
files), even in some file names
- the project is using asyncio (but it does not seem directly related at first 
look)
- it is running without issue as is on python 3.6

Here is a gdb backtrace:

```
$ gdb python
GNU gdb (GDB) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from python...(no debugging symbols found)...done.
(gdb) run trefle/bin.py 
Starting program: /home/ybon/.virtualenvs/trefle/bin/python trefle/bin.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Initializing config
Done initializing config

Program received signal SIGSEGV, Segmentation fault.
0x7791a9ce in PyObject_Malloc () from /usr/lib/libpython3.7m.so.1.0
(gdb) backtrace 
#0  0x7791a9ce in PyObject_Malloc () from /usr/lib/libpython3.7m.so.1.0
#1  0x779fec6e in ?? () from /usr/lib/libpython3.7m.so.1.0
#2  0x77a05874 in PyParser_ASTFromStringObject () from 
/usr/lib/libpython3.7m.so.1.0
#3  0x77a693f2 in Py_CompileStringObject () from 
/usr/lib/libpython3.7m.so.1.0
#4  0x77a695c3 in ?? () from /usr/lib/libpython3.7m.so.1.0
#5  0x7795963f in _PyMethodDef_RawFastCallDict () from 
/usr/lib/libpython3.7m.so.1.0
#6  0x779597d1 in _PyCFunction_FastCallDict () from 
/usr/lib/libpython3.7m.so.1.0
#7  0x779f7e16 in _PyEval_EvalFrameDefault () from 
/usr/lib/libpython3.7m.so.1.0
#8  0x77939069 in _PyEval_EvalCodeWithName () from 
/usr/lib/libpython3.7m.so.1.0
#9  0x77980982 in _PyFunction_FastCallKeywords () from 
/usr/lib/libpython3.7m.so.1.0
#10 0x779f3142 in _PyEval_EvalFrameDefault () from 
/usr/lib/libpython3.7m.so.1.0
#11 0x77939069 in _PyEval_EvalCodeWithName () from 
/usr/lib/libpython3.7m.so.1.0
#12 0x77980982 in _PyFunction_FastCallKeywords () from 
/usr/lib/libpython3.7m.so.1.0
#13 0x779f2225 in _PyEval_EvalFrameDefault () from 
/usr/lib/libpython3.7m.so.1.0
#14 0x779807db in _PyFunction_FastCallKeywords () from 
/usr/lib/libpython3.7m.so.1.0
#15 0x779f2225 in _PyEval_EvalFrameDefault () from 
/usr/lib/libpython3.7m.so.1.0
#16 0x779807db in _PyFunction_FastCallKeywords () from 
/usr/lib/libpython3.7m.so.1.0
#17 0x779f2225 in _PyEval_EvalFrameDefault () from 
/usr/lib/libpython3.7m.so.1.0
#18 0x779807db in _PyFunction_FastCallKeywords () from 
/usr/lib/libpython3.7m.so.1.0
#19 0x779f23cd in _PyEval_EvalFrameDefault () from 
/usr/lib/libpython3.7m.so.1.0
#20 0x779807db in _PyFunction_FastCallKeywords () from 
/usr/lib/libpython3.7m.so.1.0
#21 0x779f23cd in _PyEval_EvalFrameDefault () from 
/usr/lib/libpython3.7m.so.1.0
#22 0x7793a08b in _PyFunction_FastCallDict () from 
/usr/lib/libpython3.7m.so.1.0
#23 0x77949888 in ?? () from /usr/lib/libpython3.7m.so.1.0
#24 0x779b71b9 in _PyObject_CallMethodIdObjArgs () from 
/usr/lib/libpython3.7m.so.1.0
#25 0x7792e285 in PyImport_ImportModuleLevelObject () from 
/usr/lib/libpython3.7m.so.1.0
#26 0x779f4434 in _PyEval_EvalFrameDefault () from 
/usr/lib/libpython3.7m.so.1.0
#27 0x77939069 in _PyEval_EvalCodeWithName () from 
/usr/lib/libpython3.7m.so.1.0
#28 0x77939f34 in PyEval_EvalCodeEx () f

[issue34355] SIGSEGV (Address boundary error)

2018-08-08 Thread Yohan Boniface 


Yohan Boniface  added the comment:

Thanks all :)

As noted by Julien, to reproduce the test cases, one also needs to install the 
dev requirements (or just `pip instal minicli hupper`):

pip install -r requirements-dev.txt

> and what's the issue with asyncio ?

Nothing specific as far as I can tell.
I mentioned it because not all projects use asyncio so I thought it was an 
significative point to have in mind, just in case.
Also I blindly checked "asyncio" in the "Components" because the project does 
use asyncio, without foreseeing that this would point asyncio as a guilty and 
that asyncio maintainers would have been specifically CCed.
Thanks for fixing this.

One other thing to notice just in case: the code base do have unicode chars (in 
comments, strings and raw strings).

--

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