Message338469
| Author | remi.lapeyre |
|---|---|
| Recipients | asmeurer, remi.lapeyre, xtreak |
| Date | 2019-03-20.13:17:58 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1553087878.95.0.906112005465.issue36370@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
FWIW I just tried both f8e46e9e741f253803e9b8be03287e5dd16abd4d and f8e46e9e741f253803e9b8be03287e5dd16abd4d with the reproducer given and none of them segfault. I don't think there is a bug in the Python interpreter, there is some ways to trigger this error when a RecursionError is not handled quickly enough. I suppose you just have a problem in Sympy. I also find suspicious that you reproducer change many lines in Sympy and would look at that first. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-03-20 13:17:58 | remi.lapeyre | set | recipients: + remi.lapeyre, asmeurer, xtreak |
| 2019-03-20 13:17:58 | remi.lapeyre | set | messageid: <1553087878.95.0.906112005465.issue36370@roundup.psfhosted.org> |
| 2019-03-20 13:17:58 | remi.lapeyre | link | issue36370 messages |
| 2019-03-20 13:17:58 | remi.lapeyre | create | |