Jeremy, can you build your own 3.23.51? There is actually the same memory overwrite bug in gethostname_r of glibc/Linux in .49a as in .50.
If you build mysqld yourself you can run it inside gdb and do bt full when it crashes. That might help in tracing the bug. The assertion failure below means the magic number of a trx struct was wrong. A resolved stack trace might help a lot if this is not random memory corruption. Regards, Heikki ----- Original Message ----- From: "Jeremy Zawodny" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Heikki Tuuri" <[EMAIL PROTECTED]> Sent: Tuesday, May 28, 2002 9:16 PM Subject: InnoDB crash on 3.23.49a... > I just converted several tables to InnoDB on our Linux 3.23.49a > (binary from MySQL.com). After running our production system against > it for about 10 minutes, InnoDB crashed with a stack trace: > > ---snip--- > > /home/mysql/bin/mysqld: ready for connections > InnoDB: Assertion failure in thread 159781 in file ha_innobase.cc line 302 > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to [EMAIL PROTECTED] > mysqld got signal 11; > This could be because you hit a bug. It is also possible that this binary > or one of the libraries it was linked agaist 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 > > 0x806dc04 > 0x82ad1a8 > 0x80be1ca > 0x80c0aee > 0x80b4604 > 0x809f782 > 0x804ec80 > 0x806784d > 0x806d8e4 > 0x80731a1 > Stack trace seems successful - bottom reached > Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instr > uctions 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 (nil) is invalid pointer > thd->thread_id=3 > > ---snip--- > > However, there are no symbols in the mysqld binary so that I can > resolve the bug. The trace was identical both times. > > I've just converted the tables back to MyISAM and will run like this I > guess. Is anyone using the pre-release 3.23.50 in production yet? Or > should I build my own 3.23.51 and try that? > > Jeremy > -- > Jeremy D. Zawodny, <[EMAIL PROTECTED]> > Technical Yahoo - Yahoo Finance > Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 > > MySQL 4.0.2: up 0 days, processed 3,903,167 queries (96/sec. avg) --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
