Issue2084

classification
Title: RuntimeException when importing subprocess on IBM J9 VM
Type: crash Severity: normal
Components: Core Versions: Jython 2.7
Milestone:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: zyasoft Nosy List: ben_b, pekka.klarck, zyasoft
Priority: urgent Keywords:

Created on 2013-09-05.20:09:21 by ben_b, last changed 2015-03-09.18:01:27 by zyasoft.

Files
File name Uploaded Description Edit Remove
exception_stack.txt ben_b, 2013-09-05.20:09:21 exception_stack
Messages
msg8102 (view) Author: Ben (ben_b) Date: 2013-09-05.20:09:21
On IBM J9 VM, importing the subprocess module fails with a RuntimeException when the _init_signals routine attempts to test for the existence of SIGINFO.  Attached full exception stack.
msg8104 (view) Author: Jim Baker (zyasoft) Date: 2013-09-05.22:31:11
That's interesting, subprocess imports signal, which in turn probes for available signals in _init_signals(), using sun.misc.Signal. The stack trace in exception_stack.txt shows that java.lang.IllegalArgumentException is being thrown. This exception is expected if the probe fails, but for some reason it's not being caught.
msg9391 (view) Author: Jim Baker (zyasoft) Date: 2015-01-14.17:28:28
This will require debugging against J9, and should be part of the RC1 process. I checked http://www.ibm.com/developerworks/java/jdk/linux/tested.html, and Ubuntu 14.04 is supported, so I will take a look when I have a chance.
msg9552 (view) Author: Jim Baker (zyasoft) Date: 2015-02-23.04:49:46
Finally read this bug closely - the problem is that the RuntimeException is wrapping IllegalArgumentException on J9.

That's easy enough to fix: we should simply give up registering a signal name if any exception is raised, as opposed to being so precise.

Blocker for RC1, but a trivial fix
msg9565 (view) Author: Pekka Klärck (pekka.klarck) Date: 2015-02-26.07:07:42
Does this mean that RuntimeException should also be taken into account at with #1729? There we probably cannot catch all exceptions but need to be somewhat precise.
msg9568 (view) Author: Jim Baker (zyasoft) Date: 2015-03-02.01:21:05
Re #1729 - we try to be precise.  I would prefer to get a bug report that tells us what's exactly going on for a given target, vs guessing.
msg9569 (view) Author: Jim Baker (zyasoft) Date: 2015-03-02.01:29:52
Fixed as of https://hg.python.org/jython/rev/75513a17baf9
History
Date User Action Args
2015-03-09 18:01:27zyasoftsetstatus: pending -> closed
2015-03-02 01:29:52zyasoftsetstatus: open -> pending
resolution: remind -> fixed
messages: + msg9569
2015-03-02 01:21:06zyasoftsetmessages: + msg9568
2015-02-26 07:07:43pekka.klarcksetnosy: + pekka.klarck
messages: + msg9565
2015-02-23 04:49:46zyasoftsetpriority: high -> urgent
messages: + msg9552
2015-01-14 17:28:28zyasoftsetpriority: high
assignee: zyasoft
messages: + msg9391
2014-05-21 21:37:35zyasoftsetresolution: remind
2013-09-05 22:31:11zyasoftsetnosy: + zyasoft
messages: + msg8104
2013-09-05 20:09:21ben_bcreate