Bug #49183 after unclean shutdown, mysqld halts with SIGSEGV; recovery impossible
Submitted: 29 Nov 2009 4:25 Modified: 19 Jul 2010 9:00
Reporter: joe barillari Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.1.41 OS:Linux (Debian)
Assigned to: CPU Architecture:Any
Tags: innodb, segv, SIGSEGV

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[29 Nov 2009 4:25] joe barillari
My my.cnf

Attachment: my.cnf (application/octet-stream, text), 4.08 KiB.

[29 Nov 2009 4:26] joe barillari
Stderr from mysqld

Attachment: mysqld-stderr.txt (text/plain), 3.94 KiB.

[29 Nov 2009 4:28] joe barillari
GDB trace

Attachment: gdb-trace.txt (text/plain), 11.83 KiB.