On Tue, May 28, 2002 at 01:16:28PM -0700, Jeremy Zawodny wrote:
> On Tue, May 28, 2002 at 10:59:45PM +0300, Heikki Tuuri wrote:
> > 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.
>
> I'll inst
gt;
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, May 28, 2002 11:18 PM
Subject: Re: InnoDB crash on 3.23.49a...
> On Tue, May 28, 2002 at 10:59:45PM +0300, Heikki Tuuri wrote:
> > Jeremy,
> >
> > can you build your own 3.23.51? There is actually the same memory
overwrit
On Tue, May 28, 2002 at 10:59:45PM +0300, Heikki Tuuri wrote:
> 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.
Come to think of it, if that's what caused the problem, wouldn't this
"solve" it for no
On Tue, May 28, 2002 at 10:59:45PM +0300, Heikki Tuuri wrote:
> 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.
I'll install 3.23.51 tonight. I have been doing daily builds of the
3.23 and 4.0 tree
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
