Charles-Francois Natali <neolo...@free.fr> added the comment: > 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?
If you're talking about the first issue (segfaults due to writting to gil_last_holder->cpu_bound), it was occuring quite often during ccbench (pretty much anywhere malloc/free was called). I'm running a regular dual-core Linux box, nothing special. For the second one, I didn't observe any segfault, I just figured this out reading the code and confirmed it with valgrind, but it's much less likely because the race window is very short and it also requires that the page is unmmaped in between. If someone really wanted to get segfaults, I guess a good start would be: - get a fast machine, multi-core is a bonus - use a kernel with full preemption - use a lot of threads (-n option with ccbench) - use purify or valgrind --free-fill option so that you're sure to jump to noland if you dereference a previously-free'd pointer ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7946> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
