New submission from Nicholas Chammas: Python 3.5.1, OS X 10.11.3.
I have an application that uses asyncio and Cryptography (via the AsyncSSH library). Cryptography has some parts written in C, I believe. I'm testing my application by sending a keyboard interrupt while 2 tasks are working. My application doesn't clean up after itself correctly, so I get these warnings about pending tasks being destroyed, but I don't think I should ever be getting segfaults. I am able to consistently get this segfault by interrupting my application at roughly the same point. I'm frankly intimidated by the segfault (it's been many years since I dug into one), but the most likely culprits are either Python or Cryptography since they're the only components of my application that have parts written in C, as far as I know. I'm willing to help boil this down to something more minimal with some help. Right now I just have the repro at this branch of my application (which isn't too helpful for people other than myself): https://github.com/nchammas/flintrock/pull/77 Basically, launch a cluster on EC2, and as soon as one task reports that SSH is online, interrupt Flintrock with Control + C. You'll get this segfault. ---------- components: Macintosh, asyncio files: segfault.txt messages: 261036 nosy: Nicholas Chammas, gvanrossum, haypo, ned.deily, ronaldoussoren, yselivanov priority: normal severity: normal status: open title: asyncio-related (?) segmentation fault type: crash versions: Python 3.5 Added file: http://bugs.python.org/file42051/segfault.txt _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26463> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
