http://disqus.com/people/194f9871684ffc7052bb8d702448af0a/enWed, 30 Jul 2008 19:37:31 -0000http://pyjesse.disqus.com/does_anyone_know_what_this_error_is_segfault/#comment-785199Were you not able to run gdb? You can usually use it to get the stack trace of a segfault (using bt/backtrace). You have to load the Python binary with it though (and not your script), and then use "run /path/to/your/script arg1 arg2 ...".<br><br>You can also change the user limit on core dumps so a full dump is produced on a segfault using "ulimit -c unlimited", and then load that core dump into gdb with "core core.123456".Brodie RaoMon, 30 Jun 2008 18:31:28 -0000http://pyjesse.disqus.com/the_2630_multiprocessing_todo_list/#comment-1055800For memory issues on OS X I recommend using Guard Malloc. I ran into a weird memory allocation bug in Python recently that caused seemingly random crashes (see issue3242). I was able to narrow down the behavior to a consistent and more useful kind of crash with it.Brodie RaoWed, 30 Jul 2008 19:37:31 -0000