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

Ouverte
#57,882 7 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
25/100
Type d'issue
Bug
Clarté
À clarifier
Activité
À l'abandon
Stack technique
python
Domaine
operating-systems

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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']

    Langage dominant
    Python
    Étoiles
    77.2k
    Forks
    36k
    Merge moyen
    1 j 9 h
    PR mergées (30 j)
    558

    Guide de contribution

    Ouvrir le guide de contribution

    Par où commencer

    1. Lisez l'issue en entier, puis le guide de contribution du projet.
    2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
    3. Forkez le dépôt et travaillez sur une branche.
    4. Ouvrez une pull request qui référence le numéro de l'issue.

    Autres issues de python/cpython

    Toutes les issues de python/cpython

    Issues similaires

    Plus d'issues Python

    Recevez les nouvelles issues par e-mail

    Un résumé court des issues GitHub adaptées aux débutants.