homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients neologix, vstinner
Date 2011年07月01日.23:49:52
SpamBayes Score 5.0152967e-06
Marked as misclassified No
Message-id <1309564193.13.0.575056952446.issue12469@psf.upfronthosting.co.za>
In-reply-to
Content
On FreeBSD 6, os.kill(os.getpid(), signum) calls immediatly the signal handler before the creation of the first thread (which was the case by default before my commit 024827a9db64), whereas the signal handler is called "later" (when exactly?) after the creation of the first thread (default after my commit).
The traceback is sometimes "truncated" because tstate->frame is NULL. I suppose that the signal handler is called after the execution of the last instruction, after PyEval_EvalFrameEx() has set tstate->frame to f->f_back (which is NULL for the last frame).
History
Date User Action Args
2011年07月01日 23:49:53vstinnersetrecipients: + vstinner, neologix
2011年07月01日 23:49:53vstinnersetmessageid: <1309564193.13.0.575056952446.issue12469@psf.upfronthosting.co.za>
2011年07月01日 23:49:52vstinnerlinkissue12469 messages
2011年07月01日 23:49:52vstinnercreate

AltStyle によって変換されたページ (->オリジナル) /