More on: mysqld got signal 11

2001-03-08 Thread Steven Roussey
Hi! I have received several emails from people that choose not to (or can not) post to the list about mysql segfaulting. At the moment, I have the segfaults stopped by doing all of the below, I don't know (yet) which are to blame or in what combination: 1) Eliminate insert delayed (not really

RE: More on: mysqld got signal 11

2001-03-08 Thread Steven Roussey
Damn! It took longer, but crashed again. The stack trace has been the same as the last three crashes: # resolve_stack_dump -s /tmp/mysqld.sym -n mysqld.stack 0x40097532 __evoke_link_warning_llseek + 937652786 0x80b3360

Re: More on: mysqld got signal 11

2001-03-08 Thread Kyle Hayes
Most of the times I have seen signal 11 in the past, it turned out to be bad memory. Once I saw it with a bad motherboard. Another time, it was a bad stick of RAM. The bad stick was a really hard one to track down as you needed to have something really finicky get put at that address