New task #5736 in mysql: problem z mysqldump

[Flyspray - The bug killer!]

Project: PLD 2.x (Ac)

  Reported by: Łukasz Mozer (Baseciq)
      Package: mysql
      Version: 5.0.15
      Summary: problem z mysqldump
  
  próba zrobienia dumpa z bazy danych wywala się na widokach:

mysqldump: mysqldump: Couldn't execute 'show create table
`view_tpop3d`': Lost
connection to MySQL server during query (2013)

Komunikat z logów:

*** glibc detected *** double free or corruption (out): 0x4307a550 ***
mysqld got signal 6;
This could be because you hit a bug. It is also possible that this
binary
or one of the libraries it was linked against is corrupt, improperly
built,
or misconfigured. This error can also be caused by malfunctioning
hardware.
We will try our best to scrape up some info that will hopefully help
diagnose
the problem, but since we have already crashed, something is definitely
wrong
and this may fail.

key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=22
max_connections=100
threads_connected=15
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0xb7e137b8
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...
frame pointer (ebp) is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8b7fc10 = show create table `view_tpop3d`
thd->thread_id=24931
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.


For more further see:
http://bugs.pld-linux.org/index.php?do=details&id=5736

------------------------------------------------------------------------
THIS IS AN AUTOMATICALLY GENERATED MESSAGE, DO NOT REPLY