[issue35484] Segmentation fault due to faulthandler on Solaris

[Jakub Kulik]

Jakub Kulik  added the comment:

Oh, thanks for the catch, it most likely is.

--
resolution:  -> duplicate
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

[issue35484] Segmentation fault due to faulthandler on Solaris

[Peter Edwards]

Peter Edwards  added the comment:

This is likely a duplicate of issue 21131

--
nosy: +peadar

___
Python tracker 

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

[issue35484] Segmentation fault due to faulthandler on Solaris

[Jakub Kulik]

Jakub Kulik  added the comment:

The exact failing test is test_register_chain().

Output of this failed test (as expected for segmentation fault):

==
FAIL: test_register_chain (test.test_faulthandler.FaultHandlerTests)
--
Traceback (most recent call last):
  File "xxx/Python-3.7.1/Lib/test/test_faulthandler.py", line 708, in 
test_register_chain
self.check_register(chain=True)
  File "xxx/Python-3.7.1/Lib/test/test_faulthandler.py", line 686, in 
check_register
self.assertEqual(exitcode, 0)
AssertionError: -11 != 0

--

___
Python tracker 

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

[issue35484] Segmentation fault due to faulthandler on Solaris

[Jakub Kulik]

Change by Jakub Kulik :


Added file: https://bugs.python.org/file47994/reproduce.py

___
Python tracker 

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

[issue35484] Segmentation fault due to faulthandler on Solaris

[Jakub Kulik]

New submission from Jakub Kulik :

When running tests on Solaris (amd64) I noticed that one test in 
test_faulthandler.py fails with the segmentation fault.

I have attached program reproducing this issue and its core stack trace. 
Program runs entirely with *Ending* printed as well and segfaults somewhere in 
the sys.exit() during deallocation. 

Problem doesn't appear when chain variable is set to False or if faulthandler 
is unregistered. Also, this bug appears only with --enable-optimizations on, 
but probably it just doesn't manifest itself in non optimized build (or on 
sparc).

I am not sure how to diagnose it more so I am at least reporting this issue.

--
components: Extension Modules, Interpreter Core
files: crash_stack.txt
messages: 331763
nosy: kulikjak
priority: normal
severity: normal
status: open
title: Segmentation fault due to faulthandler on Solaris
type: crash
versions: Python 3.7
Added file: https://bugs.python.org/file47993/crash_stack.txt

___
Python tracker 

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