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 Ilya.Kulakov
Recipients Fynn Be, Ilya.Kulakov, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2017-11-16.18:53:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510858429.24.0.213398074469.issue31701@psf.upfronthosting.co.za>
In-reply-to
Content
I think faulthandler should use both. E.g. in [1] you can read about an exception that can be handled by AddVectoredExceptionHandler but not SetUnhandledExceptionFilter.

Perhaps implementation should use SetUnhandledExceptionFilter for everything and AddVectoredExceptionHandler only for those exceptions that cannot be handled by the former, like c0000374.

I couldn't find a list, so guess it will be an ongoing WIP.

1: https://stackoverflow.com/questions/19656946/why-setunhandledexceptionfilter-cannot-capture-some-exception-but-addvectoredexc
History
Date User Action Args
2017-11-16 18:53:49Ilya.Kulakovsetrecipients: + Ilya.Kulakov, paul.moore, vstinner, tim.golden, zach.ware, steve.dower, Fynn Be
2017-11-16 18:53:49Ilya.Kulakovsetmessageid: <1510858429.24.0.213398074469.issue31701@psf.upfronthosting.co.za>
2017-11-16 18:53:49Ilya.Kulakovlinkissue31701 messages
2017-11-16 18:53:49Ilya.Kulakovcreate