[issue37565] test_faulthandler failure

2019-07-15 Thread STINNER Victor


STINNER Victor  added the comment:

More tests.

(*) What is the output of signal.getsignal(signal.SIGUSR1) before importing 
faulthandler (before calling any faulthandler method)? Example:

$ python3
Python 3.7.3 (default, May 11 2019, 00:38:04) 
>>> import signal; signal.getsignal(signal.SIGUSR1)


(*) Can you try to run attached script in gdb? If you get a crash, type "where" 
to get the traceback. Example:

$ gdb -args ./python script.py 
(gdb) handle SIGUSR1 nostop
SignalStop  Print   Pass to program Description
SIGUSR1   NoYes Yes User defined signal 1

(gdb) run
Starting program: /home/vstinner/python/master/python script.py

Program received signal SIGUSR1, User defined signal 1.
Current thread 0x77c27740 (most recent call first):
  File "/home/vstinner/python/master/script.py", line 13 in 

Program received signal SIGUSR1, User defined signal 1.
called True
[Inferior 1 (process 24361) exited normally]

--
Added file: https://bugs.python.org/file48485/script.py

___
Python tracker 

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



[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 the related bugs I 
mentioned, I think my first comments were mixed up.  There were 2 possibly 
related bugs.

1.  Redhat bugzilla 1687171, which may have been related to the skylake 
chipset: https://bugzilla.redhat.com/show_bug.cgi?id=1687171 

2.  Github # 32:  https://github.com/vstinner/faulthandler/issues/32
That is an older one (2017), and maybe not related.

Bug # 36 at Github is one that I opened initially, and that one is a duplicate 
of this bug report. It is closed now as I was asked to open the bug here 
instead.

Thanks for any further insight or suggestions you can provide.

--

___
Python tracker 

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



[issue37565] test_faulthandler failure

2019-07-14 Thread STINNER Victor


STINNER Victor  added the comment:

> I found a similar error reported in RedHat bugzilla (1687171) and tried 
> running the script provided by Victor Stinner

Link: https://bugzilla.redhat.com/show_bug.cgi?id=1687171

> and this closed issue on GitHub seems like it might be related?
#32 because of the Skylake chipset.

I guess that you mean: https://github.com/vstinner/faulthandler/issues/36

--

___
Python tracker 

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



[issue37565] test_faulthandler failure

2019-07-14 Thread STINNER Victor


STINNER Victor  added the comment:

I don't know why you get a crash. Can you try attached sigusr1.py script? 
Expected output:

$ python3 sigusr1.py 
called True

--
Added file: https://bugs.python.org/file48479/sigusr1.py

___
Python tracker 

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



[issue37565] test_faulthandler failure

2019-07-12 Thread Jeffrey Kintscher


Change by Jeffrey Kintscher :


--
nosy: +Jeffrey.Kintscher

___
Python tracker 

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



[issue37565] test_faulthandler failure

2019-07-11 Thread Karthikeyan Singaravelan


Change by Karthikeyan Singaravelan :


--
nosy: +vstinner

___
Python tracker 

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



[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 fails with the following errors:

```
0:00:22 load avg: 3.12 [402/416/1] test_faulthandler failed
test test_faulthandler failed -- Traceback (most recent call last):
  File "/tmp/shellysw/build/Python-3.7.4/Lib/test/test_faulthandler.py", line 
724, in test_register_chain
self.check_register(chain=True)
  File "/tmp/shellysw/build/Python-3.7.4/Lib/test/test_faulthandler.py", line 
702, in check_register
self.assertEqual(exitcode, 0)
AssertionError: -11 != 0
```

I found a similar error reported in RedHat bugzilla (1687171) and tried running 
the script provided by Victor Stinner, and this closed issue on GitHub seems 
like it might be related?
#32 because of the Skylake chipset.

Script:
```
import faulthandler, signal, os

def handler(signum, frame):
handler.called = True
handler.called = False

faulthandler.enable()

signum = signal.SIGUSR1
signal.signal(signum, handler)
faulthandler.register(signum, chain=True)
os.kill(os.getpid(), signum)
print("called", handler.called)
```

It produced a segmentation fault. I also ran that script using the python 3.6.6 
binary that came installed with centos and it also produced a segmentation 
fault as well.

--
components: Build, Tests
messages: 347688
nosy: jshelly
priority: normal
severity: normal
status: open
title: test_faulthandler failure
type: compile error
versions: Python 3.7

___
Python tracker 

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