[issue37565] test_faulthandler: test_register_chain() crash with SIGSEGV (signal 11) on Skylake chipset

2019-07-16 Thread Michelle Johnson
Michelle Johnson added the comment: Is the problem I'm seeing possibly related to this issue: https://bugs.python.org/issue21131 It seems to share a lot of similarities. -- ___ Python tracker <https://bugs.python.org/issue37

[issue37565] test_faulthandler: test_register_chain() crash with SIGSEGV (signal 11) on Skylake chipset

2019-07-15 Thread Michelle Johnson
Michelle Johnson added the comment: Oh, ok. So, it doesn't seem like trying to get the contents of op was successful: (gdb) print *op $1 = {ob_refcnt = 0, ob_type = 0x0} (gdb) print *op->ob_type Cannot access memory at address 0x0 (gdb) I then followed your instructions to recomp

[issue37565] test_faulthandler: test_register_chain() crash with SIGSEGV (signal 11) on Skylake chipset

2019-07-15 Thread Michelle Johnson
Michelle Johnson added the comment: 1. Here is the output of the signal.getsignal test: [jshelly@gl-build bin]$ ./python3 Python 3.7.4 (default, Jul 15 2019, 10:08:37) [GCC 8.2.0] on linux Type "help", "copyright", "credits" or "license"

[issue37565] test_faulthandler failure

2019-07-15 Thread Michelle Johnson
Michelle Johnson added the comment: Hello Victor. Thank you for looking into this. I ran the attached script, sigusr1.py as you requested. The output was as expected: [jshelly@gl-build bin]$ ./python3.7 ~/sigusr1.py called True Not sure if that helps identify the problem. Regarding

[issue37565] test_faulthandler failure

2019-07-11 Thread Michelle Johnson
New submission from Michelle Johnson : CentOS 7.6, running Linux gl-build.arc-ts.umich.edu 3.10.0-957.10.1.el7.x86_64 #1 SMP Mon Mar 18 15:06:45 UTC 2019 x86_64 on Intel(R) Xeon(R) Gold 6140 CPU @ 2.30GHz. Using gcc 8.2.0 compiled from source to build python 3.7.4 from source, make test