Package: mysql-server-5.0
Version: 5.0.32-3

Hi,

I was playing around with the CMS Joomla! Version 1.0.12.
While clicking around in the admin panel the mysql server crashed.
I have a log of the crash and I have done a stack trace like described on the 
mysql page.
I can reproduce this error. I allready deleted the database and recreated it, 
but get the same error.

Log of the crash:
Feb 12 02:08:34 server mysqld[31084]: mysqld got signal 6;
Feb 12 02:08:34 server mysqld[31084]: This could be because you hit a bug. It 
is also possible that this binary
Feb 12 02:08:34 server mysqld[31084]: or one of the libraries it was linked 
against is corrupt, improperly built,
Feb 12 02:08:34 server mysqld[31084]: or misconfigured. This error can also be 
caused by malfunctioning hardware.
Feb 12 02:08:34 server mysqld[31084]: We will try our best to scrape up some 
info that will hopefully help diagnose
Feb 12 02:08:34 server mysqld[31084]: the problem, but since we have already 
crashed, something is definitely wrong
Feb 12 02:08:34 server mysqld[31084]: and this may fail.
Feb 12 02:08:34 server mysqld[31084]:
Feb 12 02:08:34 server mysqld[31084]: key_buffer_size=16777216
Feb 12 02:08:34 server mysqld[31084]: read_buffer_size=131072
Feb 12 02:08:34 server mysqld[31084]: max_used_connections=3
Feb 12 02:08:34 server mysqld[31084]: max_connections=100
Feb 12 02:08:34 server mysqld[31084]: threads_connected=1
Feb 12 02:08:34 server mysqld[31084]: It is possible that mysqld could use up to
Feb 12 02:08:34 server mysqld[31084]: key_buffer_size + (read_buffer_size + 
sort_buffer_size)*max_connections = 233983 K
Feb 12 02:08:34 server mysqld[31084]: bytes of memory
Feb 12 02:08:34 server mysqld[31084]: Hope that's ok; if not, decrease some 
variables in the equation.
Feb 12 02:08:34 server mysqld[31084]:
Feb 12 02:08:34 server mysqld[31084]: thd=0x8ad8b98
Feb 12 02:08:34 server mysqld[31084]: Attempting backtrace. You can use the 
following information to find out
Feb 12 02:08:34 server mysqld[31084]: where mysqld died. If you see no messages 
after this, something went
Feb 12 02:08:34 server mysqld[31084]: terribly wrong...
Feb 12 02:08:34 server mysqld[31084]: Cannot determine thread, fp=0xb3f58ab8, 
backtrace may not be correct.
Feb 12 02:08:34 server mysqld[31084]: Stack range sanity check OK, backtrace 
follows:
Feb 12 02:08:34 server mysqld[31084]: 0x81c0649
Feb 12 02:08:34 server mysqld[31084]: 0xb7f68410
Feb 12 02:08:34 server mysqld[31084]: 0xb7cc2fb9
Feb 12 02:08:34 server mysqld[31084]: 0xb7cf6c8a
Feb 12 02:08:34 server mysqld[31084]: 0xb7cfe51f
Feb 12 02:08:34 server mysqld[31084]: 0xb7cfe5c2
Feb 12 02:08:34 server mysqld[31084]: 0x8484df3
Feb 12 02:08:34 server mysqld[31084]: 0x820a289
Feb 12 02:08:34 server mysqld[31084]: 0x8213c65
Feb 12 02:08:34 server mysqld[31084]: 0x82bf766
Feb 12 02:08:34 server mysqld[31084]: 0x8221b48
Feb 12 02:08:34 server mysqld[31084]: 0x822244e
Feb 12 02:08:34 server mysqld[31084]: 0x81d7495
Feb 12 02:08:34 server mysqld[31084]: 0x81dba07
Feb 12 02:08:34 server mysqld[31084]: 0x81dbec0
Feb 12 02:08:34 server mysqld[31084]: 0x81dd188
Feb 12 02:08:34 server mysqld[31084]: 0x81ddb94
Feb 12 02:08:34 server mysqld[31084]: 0xb7f29240
Feb 12 02:08:34 server mysqld[31084]: 0xb7d6432e
Feb 12 02:08:34 server mysqld[31084]: New value of fp=(nil) failed sanity 
check, terminating stack trace!
Feb 12 02:08:34 server mysqld[31084]: Please read 
http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow 
instructions on how to resolve the stack trace. Resolved
Feb 12 02:08:34 server mysqld[31084]: stack trace is much more helpful in 
diagnosing the problem, so please do
Feb 12 02:08:34 server mysqld[31084]: resolve it
Feb 12 02:08:34 server mysqld[31084]: Trying to get some variables.
Feb 12 02:08:34 server mysqld[31084]: Some pointers may be invalid and cause 
the dump to abort...
Feb 12 02:08:34 server mysqld[31084]: thd->query at 0x8b405c0 = SELECT  c.*, 
c.checked_out as checked_out_contact_category, g.name AS groupname, u.name AS 
editor,COUNT( DISTINCT s2.checked_out ) AS checked_out
Feb 12 02:08:34 server mysqld[31084]:  , z.title AS section_name
Feb 12 02:08:34 server mysqld[31084]:  FROM jos_categories AS c
Feb 12 02:08:34 server mysqld[31084]:  LEFT JOIN jos_users AS u ON u.id = 
c.checked_out
Feb 12 02:08:34 server mysqld[31084]:  LEFT JOIN jos_groups AS g ON g.id = 
c.access
Feb 12 02:08:34 server mysqld[31084]:  LEFT JOIN `jos_content` AS s2 ON 
s2.catid = c.id AND s2.checked_out > 0
Feb 12 02:08:34 server mysqld[31084]:  LEFT JOIN jos_sections AS z ON z.id = 
c.section
Feb 12 02:08:34 server mysqld[31084]:  WHERE c.section NOT LIKE '%com_%'
Feb 12 02:08:34 server mysqld[31084]:  AND c.published != -2
Feb 12 02:08:34 server mysqld[31084]:  GROUP BY c.id
Feb 12 02:08:34 server mysqld[31084]:  ORDER BY c.section, c.ordering, c.name
Feb 12 02:08:34 server mysqld[31084]: LIMIT 30
Feb 12 02:08:34 server mysqld[31084]: thd->thread_id=17
Feb 12 02:08:34 server mysqld[31084]: The manual page at 
http://www.mysql.com/doc/en/Crashing.html 

Stack trace:
resolve_stack_dump -s mysqld.sym -n stack
0x81c0649 handle_segfault + 681
0xb7f68410 _end + -1350043328
0xb7cc2fb9 _end + -1352817431
0xb7cf6c8a _end + -1352605254
0xb7cfe51f _end + -1352574385
0xb7cfe5c2 _end + -1352574222
0x8484df3 free_root + 67
0x820a289 _Z14free_tmp_tableP3THDP8st_table + 201
0x8213c65 _ZN4JOIN7destroyEv + 165
0x82bf766 _ZN13st_select_lex7cleanupEv + 38
0x8221b48 
_Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_sel
 + 152
0x822244e _Z13handle_selectP3THDP6st_lexP13select_resultm + 318
0x81d7495 _Z21mysql_execute_commandP3THD + 9557
0x81dba07 _Z11mysql_parseP3THDPcj + 471
0x81dbec0 _Z16dispatch_command19enum_server_commandP3THDPcj + 1120
0x81dd188 _Z10do_commandP3THD + 136
0x81ddb94 handle_one_connection + 2308
0xb7f29240 _end + -1350301840
0xb7d6432e _end + -1352157090

Regards
Michael

-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to