10 messages in com.mysql.lists.bugsRe: Bug in 3.23.42 on Linux
FromSent OnAttachments
Martin MOKREJŠ29 Oct 2001 13:38 
Sasha Pachev29 Oct 2001 16:47 
Martin MOKREJŠ30 Oct 2001 02:05 
Michael Widenius30 Oct 2001 04:34 
Martin MOKREJŠ31 Oct 2001 06:35 
Martin MOKREJŠ31 Oct 2001 06:54 
Michael Widenius31 Oct 2001 11:39 
Michael Widenius31 Oct 2001 11:43 
Martin MOKREJŠ01 Nov 2001 04:55 
Michael Widenius01 Nov 2001 11:12 
Subject:Re: Bug in 3.23.42 on Linux
From:Martin MOKREJŠ (mmok@natur.cuni.cz)
Date:11/01/2001 04:55:32 AM
List:com.mysql.lists.bugs

On Wed, 31 Oct 2001, Michael Widenius wrote:

Yes, the above stack trace doesn't make sence. On the other hand, if you are using the old 3.23.41 binary instead of the 3.23.42 binary, then this could be reason for your problems.

Any change you could try to do this from the beginning ?

- Remove everying from libexec and the bin directory - Download the 3.23.43 binary (Just to make things even more interesting :) - Install and run the above.

In this case we know that your .sym file will correspiond with the binary you are using.

Well, it's clear what's going on. The stack trace from logfile corresponds to previous instalation of mysql. Current 3.23.42 is installed properly, if I omit existence of libexec/mysqld, which is not being used anyway.

I'll reinstall from scratch, sure. But we miss a chance to find thios bug, who know if it appears. ;)

The problem is that I CANNOT resolve the stack trace anymore. I don't have the right mysqld. Can you try to resove the trace using mysqld.sym.gz from your binary distribution?

The stack trace is either from a patched 3.23.41 (in such a case I'd try to dig out from tape the old installation) or (and it's more probbable) it is from oficial 3.23.41 binaries - tar.gz for all Linuxes (intel).

Could you please try the mysqld.sym.gz from 3.23.41 bindist and check, if the resolved stack makes sense? Thanks.

I'm working remotely on this problem and have a bit inconvenient access. ;)