Hi,

Sorry to have bothered everyone. I was using .38.  I just noticed that and
am currently building .40.

Cal
http://www.calevans.com


-----Original Message-----
From: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
Sent: Saturday, August 04, 2001 9:59 AM
To: Sinisa Milivojevic; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Bug report.


Hi!

What InnoDB version you are using? A bad rollback
bug was fixed in version 3.23.39.

Regards,

Heikki

At 05:40 PM 8/4/01 +0300, you wrote:
>Content-Type: message/rfc822
>Content-Description: forwarded message
>Content-Transfer-Encoding: 7bit
>
>MIME-Version: 1.0
>Content-Type: text/plain;
>       charset="iso-8859-1"
>Subject: Bug report.
>From: "Cal Evans" <[EMAIL PROTECTED]>
>To: "Mysql" <[EMAIL PROTECTED]>
>Date: Sat, 4 Aug 2001 09:25:55 -0500
>
>I have a reproducible but it's not easy to reproduce. It involves a complex
>transaction that gets rolled back instead of committed.
>
>Cal
>
>Innobase: Assertion failure in thread 8201 in file trx0roll.c line 887
>Innobase: we intentionally generate a memory trap.
>Innobase: Send a bug report to [EMAIL PROTECTED]
>mysqld got signal 11;
>The manual section 'Debugging a MySQL server' tells you how to use a
>stack trace and/or the core file to produce a readable backtrace that may
>help in finding out why mysqld died.
>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:
>0x4007c552
>0x8178fea
>0x813d2b7
>0x813dc9e
>0x8177851
>0x8179310
>0x811aaec
>0x81122b1
>0x80d3233
>0x80d4889
>0x80cfc39
>0x80cf16e
>Stack trace successful, trying to get some variables.
>Some pointers may be invalid and cause the dump to abort...
>thd->query at 0x83540c0 = rollback
>thd->thread_id = 1
>Successfully dumped variables, if you ran with --log,
>take a look at the details of what thread 1 did to cause the crash.
>In some cases of really bad corruption, this value may be invalid
>Please use the information above to create a repeatable
>test case for the crash, and send it to [EMAIL PROTECTED]
>
>Cal
>http://www.calevans.com
>
>
>
>---------------------------------------------------------------------
>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
>
>
>Content-Type: text/plain; charset=us-ascii
>Content-Description: message body and .signature
>Content-Transfer-Encoding: 7bit
>
>
>Something for you ...
>
>--
>Regards,
>   __  ___     ___ ____  __
>  /  |/  /_ __/ __/ __ \/ /    Mr. Sinisa Milivojevic <[EMAIL PROTECTED]>
> / /|_/ / // /\ \/ /_/ / /__   MySQL AB, FullTime Developer
>/_/  /_/\_, /___/\___\_\___/   Larnaca, Cyprus
>       <___/   www.mysql.com
>



---------------------------------------------------------------------
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

Reply via email to