Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Stack range sanity check OK, backtrace follows:
0x806fcf4
0x81219e8
0x814a4b6
0x814a3a3
0x819a3f4
0x8092286
0x808e4a5
0x80769a0
0x807aacc
0x8075b55
0x8074ef7
Stack trace seems successful - bottom reached
Please read
http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8315ad0 = select Distinct R.id, recipename, contributer, photo, source, counter,S.score/S.number_votes as rate from recipes_recipes R LEFT JOIN recipes_score S ON(R.id=S.id) LEFT join recipes_recipes_categories_rl C ON(R.id=C.id) LEFT join recipes_categories N ON(N.id=C.cat_id) limit 30, 30
thd->thread_id=47
Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 47 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid
The manual page at
http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
Partager