Comment 1 for bug 652990

It is very likely to be some kind of case where it thinks something exists that doesn't. Although it should not be attempting to look at triggers or stored procs.

Is it possible you could run:

shell> gdb --args drizzledump -p3306 -uroot -P<omitted>

Then in the gdb console:

gdb> run

And when it segfaults:

gdb> bt

This should give a stack of where it failed. I suspect it is an unhandled error condition (but I'm kinda hoping its not). Most likely trying to find out about whatever table comes after BlogPosts.