Message 195523 - Python tracker

Message195523

➜

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	ionelmc, neologix, pitrou, vstinner
Date	2013-08-17.21:59:09
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAMpsgwaU+XzHqJinOOT8cbUQXeVZQr+r=RW+3PSUTXjZZW9+ZQ@mail.gmail.com>
In-reply-to	<CANkHFr_13ANzfAu2aNt1igH_Czx9nQO=L4g2UOvSv7psy4_rpg@mail.gmail.com>

Content
2013/8/17 Maries Ionel Cristian <report@bugs.python.org>: > I don't think it's that obscure ... uwsgi has this issue > https://www.google.com/search?q=libgcc_s.so.1+must+be+installed+for+pthread_cancel+to+work+uwsgi+site:lists.unbit.it- > they cause it probably different but the point is that it's not > obscure. The error message is maybe the same, the reason is completly different: http://lists.unbit.it/pipermail/uwsgi/2013-July/006213.html "IT WAS A limit-as issue" The root cause is an arbitrary limit on the size of the virtual memory. Here the bug is that a thread B closes a file descriptor opened in a thread B by the glibc.

Content

2013/8/17 Maries Ionel Cristian <report@bugs.python.org>:
> I don't think it's that obscure ... uwsgi has this issue
> https://www.google.com/search?q=libgcc_s.so.1+must+be+installed+for+pthread_cancel+to+work+uwsgi+site:lists.unbit.it-
> they cause it probably different but the point is that it's not
> obscure.

The error message is maybe the same, the reason is completly different:
http://lists.unbit.it/pipermail/uwsgi/2013-July/006213.html
"IT WAS A limit-as issue"

The root cause is an arbitrary limit on the size of the virtual memory.

Here the bug is that a thread B closes a file descriptor opened in a
thread B by the glibc.

History
Date	User	Action	Args
2013-08-17 21:59:09	vstinner	set	recipients: + vstinner, pitrou, ionelmc, neologix
2013-08-17 21:59:09	vstinner	link	issue18748 messages
2013-08-17 21:59:09	vstinner	create