that's pretty nasty... the best (only...) way to try to get to the bottom of it would be to run it through the GNU Debugger
# gdb --args "the command you ran"
this will be able to catch the segfaults and once it's crashed, enter "bt" to print the backtrace stack, which should tell you what part actually did segfault.. frequently what you get is less than useless, but it's worth a try....
if all else fails, just upgrade anything you feel might be relevant.
|