MySQL Bugs: #34724: mysql crashed due to innodb null pointer difference

Bug #34724	mysql crashed due to innodb null pointer difference
Submitted:	21 Feb 2008 12:24	Modified:	7 May 2008 10:03
Reporter:	kris dba	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.1.22	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	mysqld got signal 11;trying to access a stray pointer(nil)

Description:
Mysql got crashed while doing bulkupdates on one of the table.

InnoDB: Error: trying to access a stray pointer (nil)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
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 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.

How to repeat:
NA

Thank you for a problem report. Do you have any ideas on how to repeat this crash? What kind of bul update do you perfrom?

Please add a small test that we can reproduce your szenario.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Kris,

for analysing your problem we need to know exactly what you did to get this szenario.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".