➜

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 barry
Recipients barry, pitrou, rhettinger, serhiy.storchaka, skrah, vstinner
Date 2017-09-05.23:30:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <78D40846-737B-4980-910F-CF354D9C2AC6@python.org>
In-reply-to <1504652825.03.0.604793132684.issue31338@psf.upfronthosting.co.za>
Content 
On Sep 5, 2017, at 16:07, STINNER Victor <report@bugs.python.org> wrote:
> 
> STINNER Victor added the comment:
> 
>> Neither gcc (macOS, Ubuntu), nor clang (Ubuntu) complain.
> 
> Ok, cool. In that case, go ahead.

I checked with @steve.dower and I think abort() will work on MSVC too.  He did have the idea to #define it to `Py_FatalError(“some message”); abort();` but since the former calls the latter we could get warnings that the second abort() isn’t reachable.

I say we start with abort() as the expansion and go from there.  Since it’s a macro it’s easy to redefine if you want to crank up debugging, add a breakpoint, add __LINE__ and __FILE__ or need something special for some particular compiler.
History
Date User Action Args
2017-09-05 23:30:45barrysetrecipients: + barry, rhettinger, pitrou, vstinner, skrah, serhiy.storchaka
2017-09-05 23:30:45barrylinkissue31338 messages
2017-09-05 23:30:45barrycreate