: ret
End of assembler dump.
(gdb)
List:MySQL General Discussion« Previous MessageNext Message »
From:Michael BacarellaDate:January 26 2004 6:21pm
Subject:Re: MySQL 3.23.58 seg faults occasionally
the crashes below happen in independent areas of code. The 2 first are
inside
trx_rseg_get_on_id+30: pop%ebp
0x81fa94f trx_rseg_get_on_id+31: ret
End of assembler dump.
(gdb)
List:MySQL General Discussion« Previous MessageNext Message »
From:Michael BacarellaDate:January 26 2004 6:21pm
Subject:Re: MySQL 3.23.58 seg faults occasionally
the crashes below happen in independent areas of code. The 2 first are
inside InnoDB, and the third inside MySQL. This looks like random thread
crashes, or random memory corruption.
My colleague tells me that the third stack trace (the one inside MySQL)
is from a RESET MASTER. This
Michael,
the crashes below happen in independent areas of code. The 2 first are
inside InnoDB, and the third inside MySQL. This looks like random thread
crashes, or random memory corruption.
I assume that you have my.cnf set so that the memory usage cannot approach 2
GB.
You are running a
the crashes below happen in independent areas of code. The 2 first are
inside InnoDB, and the third inside MySQL. This looks like random thread
crashes, or random memory corruption.
My colleague tells me that the third stack trace (the one inside MySQL)
is from a RESET MASTER. This server
First we cut to the chase with a resolved stack trace from
the most recent crash:
0x80c23d5 handle_segfault__Fi + 425
0x40022f54 _end + 935506260
0x822cdef btr_search_build_page_hash_index + 4771
0x82281c3 btr_search_info_update_slow + 919
0x8213f9e btr_cur_search_to_nth_level + 3154
0x81e9dce
