Message104320
| Author |
dabeaz |
| Recipients |
DazWorrall, aconrad, alex, andrix, brian.curtin, carljm, coderanger, cool-RR, dabeaz, djc, donaldjeo, durin42, eric.araujo, eric.smith, flox, gregory.p.smith, jcea, jhylton, karld, kevinwatters, konryd, larry, loewis, mahmoudimus, movement, neologix, nirai, pitrou, rcohen, rh0dium, tarek, thouis, ysj.ray |
| Date |
2010年04月27日.13:44:44 |
| SpamBayes Score |
1.3541731e-08 |
| Marked as misclassified |
No |
| Message-id |
<1272375885.82.0.776192486581.issue7946@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I stand corrected. However, I'm going to have to think of a completely different approach for carrying out that functionality as I don't know how the take_gil() function is able to determine whether gil_last_holder has been deleted or not. Will think about it and post an updated patch later.
Do you have any examples or insight you can provide about how these segfaults have shown up in Python code? I'm not able to observe any such behavior on OS-X or Linux. Is this happening while running the ccbench program? Some other program? |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年04月27日 13:44:45 | dabeaz | set | recipients:
+ dabeaz, loewis, jhylton, gregory.p.smith, jcea, pitrou, movement, larry, eric.smith, kevinwatters, tarek, djc, karld, carljm, coderanger, durin42, eric.araujo, nirai, alex, andrix, konryd, brian.curtin, flox, DazWorrall, cool-RR, rh0dium, rcohen, mahmoudimus, aconrad, ysj.ray, neologix, thouis, donaldjeo |
| 2010年04月27日 13:44:45 | dabeaz | set | messageid: <1272375885.82.0.776192486581.issue7946@psf.upfronthosting.co.za> |
| 2010年04月27日 13:44:44 | dabeaz | link | issue7946 messages |
| 2010年04月27日 13:44:44 | dabeaz | create |
|