Florian Bruhin added the comment: Hmm, fair point. I thought I had seen this being used in a SEGV handler in some other software I use, but I can't find that anymore - so either I was dreaming, or they noticed it was problematic and removed it again.
I'm closing this then. My goal was to get more useful crash reports from users (who typically don't want to install/attach gdb and reproduce the bug again, if even possible), but I guess my only remaining option is automatically getting the stacktrace from "coredumpctl" on the next start, at least on Linux systems using systemd... ---------- resolution: -> wont fix _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30998> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
