PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

Offen
#57,882 7 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
25/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
operating-systems

Rechercherichtung

Start by reviewing testsigint.zip and the attached traceback_checksignals.patch files, then inspect the current implementation of PyTraceBack_Print() and PyErr_CheckSignals(). Reproduce the signal-handling failure and compare the behavior with the proposed patches; done means the traceback prints correctly when a signal is pending but PyErr_CheckSignals() has not been called.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

interpreter-core type-bug
BPO 13673
Nosy @amauryfa, @pitrou
Files
  • testsigint.zip
  • traceback_checksignals.patch
  • traceback_checksignals_2.patch
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
closed_at = None
created_at = <Date 2011-12-28.21:34:59.902>
labels = ['interpreter-core', 'type-bug']
title = 'PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called'
updated_at = <Date 2015-10-13.04:38:39.190>
user = 'https://bugs.python.org/sbt'

    bugs.python.org fields:

    activity = <Date 2015-10-13.04:38:39.190>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2011-12-28.21:34:59.902>
creator = 'sbt'
dependencies = []
files = ['24100', '24106', '24177']
hgrepos = []
issue_num = 13673
keywords = ['patch']
message_count = 7.0
messages = ['150319', '150328', '150331', '150340', '150342', '150352', '150875']
nosy_count = 3.0
nosy_names = ['amaury.forgeotdarc', 'pitrou', 'sbt']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue13673'
versions = ['Python 2.7', 'Python 3.2', 'Python 3.3']

    Vorherrschende Sprache
    Python
    Sterne
    77.2k
    Forks
    36k
    Ø Merge
    1 T. 9 Std.
    Gemergte PRs (30 T.)
    558

    Beitragsleitfaden

    Beitragsleitfaden öffnen

    Erste Schritte

    1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
    2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
    3. Forken Sie das Repository und arbeiten Sie in einem Branch.
    4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

    Mehr aus python/cpython

    Alle Issues in python/cpython

    Ähnliche Issues

    Weitere Issues zu Python

    Neue Issues direkt in Ihr Postfach

    Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.