Message199540
| Author | neologix |
|---|---|
| Recipients | christian.heimes, neologix, pitrou, r.david.murray, sbt, vstinner |
| Date | 2013-10-12.05:58:50 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAH_1eM3KhT=4_wYF8bhhfwNHWwGSQhww_dj53Hm_NJ9fMSmY7Q@mail.gmail.com> |
| In-reply-to | <CAH_1eM2G9XQAXKJxGj4m714GcV2bmJu1_eqH+6crRiTjRe+JWw@mail.gmail.com> |
| Content | |
|---|---|
> Here is a more useful traceback: If the failures aren't linked to ENFILE, then you could use strace to find the process on which the test is doing a waitpid(), and then perform an strace and gdb on that process to see where it's stuck. And send it a fatal signal that will make faulthander dump the stack. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-10-12 05:58:50 | neologix | set | recipients: + neologix, pitrou, vstinner, christian.heimes, r.david.murray, sbt |
| 2013-10-12 05:58:50 | neologix | link | issue19227 messages |
| 2013-10-12 05:58:50 | neologix | create | |