MySQL 3.23.53 non-functional with glibc-2.3.1 on powerpc

Greetings,

After installing glibc-2.3.1 on our ppc machine (SMP macintosh G4), we
noticed that MySQL segfaults upon any connection attempt, although it
starts up without incident and restarts after the segv. The previous
configuration was no different except it was using glibc-2.2.5 and mysql
ran perfectly. We've recompiled it several times with less
optimization, etc.. but still get the same results.

Here is a partial bug-report form.

Release: mysql-3.23.53 (Source distribution)

>Environment:

System: Linux spicymeatball 2.4.20-rc1-ben0 #1 SMP Sun Nov 3 18:20:57
EST 2002 ppc unknown
Architecture: ppc

Some paths: /usr/local/bin/perl /usr/bin/make /usr/bin/gmake
/usr/bin/gcc /usr/bin/cc
GCC: Reading specs from
/usr/lib/gcc-lib/powerpc-unknown-linux-gnu/2.95.3/specs
gcc version 2.95.3 20010315 (release)
Compilation info: CC='gcc' CFLAGS='-O3 -mcpu=7400 -mpowerpc-gfxopt
-mpowerpc-gpopt' CXX='gcc' CXXFLAGS='-O3 -mcpu=7400 -mpowerpc-gfxopt
-mpowerpc-gpopt -felide-constructors -fno-exceptions -fno-rtti' LDFLAGS=''
LIBC:
lrwxrwxrwx 1 root root 13 Nov 10 23:49 /lib/libc.so.6
-> libc-2.3.1.so
-rwxr-xr-x 1 root root 5333260 Nov 8 22:13 /lib/libc-2.3.1.so
-rw-r--r-- 1 root root 25478822 Nov 8 22:12 /usr/lib/libc.a
-rw-r--r-- 1 root root 178 Nov 10 23:49 /usr/lib/libc.so
Configure command: ./configure --prefix=/usr/local/mysql
--enable-assembler --with-mysqld-ldflags=-all-static --disable-shared
--with-extra-charsets=complex 'CFLAGS=-O3 -mcpu=7400 -mpowerpc-gfxopt
-mpowerpc-gpopt' 'CXXFLAGS=-O3 -mcpu=7400 -mpowerpc-gfxopt
-mpowerpc-gpopt -felide-constructors -fno-exceptions -fno-rtti' CXX=gcc

How-To-Repeat: Attempt to connect to the MySQL server running with
glibc-2.3.1

thanks,

Ethan




------------------------------------------------------------ ---------
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 bugs-thread12947@lists.mysql.com
To unsubscribe, e-mail

Re: MySQL 3.23.53 non-functional with glibc-2.3.1 on powerpc

Ethan writes:
> Greetings,
>
> After installing glibc-2.3.1 on our ppc machine (SMP macintosh G4), we
> noticed that MySQL segfaults upon any connection attempt, although it
> starts up without incident and restarts after the segv. The previous
> configuration was no different except it was using glibc-2.2.5 and mysql
> ran perfectly. We've recompiled it several times with less
> optimization, etc.. but still get the same results.
>
> Here is a partial bug-report form.
>
> Release: mysql-3.23.53 (Source distribution)
>
> How-To-Repeat: Attempt to connect to the MySQL server running with
> glibc-2.3.1
>
> thanks,
>
> Ethan

Thank you for your bug report, but we do not test our server versus
2.3.* libraries, as those are not stable yet.

We yet have to check for the stability of 2.3.

--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
/ /|_/ / // /\ \/ /_/ / /__ 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 bugs-thread12949@lists.mysql.com
To unsubscribe, e-mail

Re: MySQL 3.23.53 non-functional with glibc-2.3.1 on powerpc

On Monday 11 November 2002 19:34, Ethan wrote:
> Greetings,
>=20
> After installing glibc-2.3.1 on our ppc machine (SMP macintosh G4), we
> noticed that MySQL segfaults upon any connection attempt, although it=20
> starts up without incident and restarts after the segv. The previous
> configuration was no different except it was using glibc-2.2.5 and mysq=
l
> ran perfectly. We've recompiled it several times with less
> optimization, etc.. but still get the same results.
>=20

I would add just a few words to Sinisa's reply.

We recently had some issues with recent RedHat Glibc 2.2.5. =20
It was due to incompatible change in RedHat Glibc and they reverted this=20
change in the last Glibc update.

It is possible the issue with GLIBC 2.3.1 is the same.=20

The problem is MySQL limits stack size to very low value (32768) at some=
=20
point which is not enough for new GLIBC. =20

If you need to use this GLIBC you may patch MySQL to use 128K+ thread sta=
cks.

It is done in mysqld.cc by pthread_attr_setstacksize() call


--=20
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Peter Zaitsev
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Moscow, Russia
<___/ www.mysql.com M: +7 095 725 4955


------------------------------------------------------------ ---------
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 bugs-thread12967@lists.mysql.com
To unsubscribe, e-mail

Re: MySQL 3.23.53 non-functional with glibc-2.3.1 on powerpc

Thank you, I'll give this a try!

Ethan

Peter Zaitsev wrote:

>On Monday 11 November 2002 19:34, Ethan wrote:
>
>
>>Greetings,
>>
>>After installing glibc-2.3.1 on our ppc machine (SMP macintosh G4), we
>>noticed that MySQL segfaults upon any connection attempt, although it
>>starts up without incident and restarts after the segv. The previous
>>configuration was no different except it was using glibc-2.2.5 and mysql
>>ran perfectly. We've recompiled it several times with less
>>optimization, etc.. but still get the same results.
>>
>>
>>
>
>I would add just a few words to Sinisa's reply.
>
>We recently had some issues with recent RedHat Glibc 2.2.5.
>It was due to incompatible change in RedHat Glibc and they reverted this
>change in the last Glibc update.
>
>It is possible the issue with GLIBC 2.3.1 is the same.
>
>The problem is MySQL limits stack size to very low value (32768) at some
>point which is not enough for new GLIBC.
>
>If you need to use this GLIBC you may patch MySQL to use 128K+ thread stacks.
>
>It is done in mysqld.cc by pthread_attr_setstacksize() call
>
>
>
>



------------------------------------------------------------ ---------
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 bugs-thread12968@lists.mysql.com
To unsubscribe, e-mail

Re: MySQL 3.23.53 non-functional with glibc-2.3.1 on powerpc

Interestingly, modifying this variable allowed the server to start (I
raised it to 131072, and also even tried 262144), and issuing a "use
database" worked as well, but a simple "select (10*10);" again caused
the server to crash.
I guess I'll have to wait to upgrade to glibc-2.3.1

Thanks,

Ethan

Peter Zaitsev wrote:

>On Monday 11 November 2002 19:34, Ethan wrote:
>
>
>>Greetings,
>>
>>After installing glibc-2.3.1 on our ppc machine (SMP macintosh G4), we
>>noticed that MySQL segfaults upon any connection attempt, although it
>>starts up without incident and restarts after the segv. The previous
>>configuration was no different except it was using glibc-2.2.5 and mysql
>>ran perfectly. We've recompiled it several times with less
>>optimization, etc.. but still get the same results.
>>
>>
>>
>
>I would add just a few words to Sinisa's reply.
>
>We recently had some issues with recent RedHat Glibc 2.2.5.
>It was due to incompatible change in RedHat Glibc and they reverted this
>change in the last Glibc update.
>
>It is possible the issue with GLIBC 2.3.1 is the same.
>
>The problem is MySQL limits stack size to very low value (32768) at some
>point which is not enough for new GLIBC.
>
>If you need to use this GLIBC you may patch MySQL to use 128K+ thread stacks.
>
>It is done in mysqld.cc by pthread_attr_setstacksize() call
>
>
>
>



------------------------------------------------------------ ---------
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 bugs-thread12972@lists.mysql.com
To unsubscribe, e-mail