Re: MySQL 4.1 SIGBUS failiure with FreeBSD 6.0
Glenn Nielsen <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.database |
|---|---|
| Message-ID | <[email protected]> |
Thanks for the reply. I had run across most of your links below in my Google search. Today I am going to try and reproduce the bug on a test box. If I can reproduce the bug the first thing I will try is building mysql with linux threads to see if that solves the problem. Glenn On Thu, Mar 23, 2006 at 06:48:31AM +0100, Kurt Jaeger wrote: > Hi! > > On Wed, Mar 22, 2006 at 03:51:10PM -0600, Glenn Nielsen wrote: > > MySQL 4.1 SIGBUS failiure with FreeBSD 6.0 > [...] > > (gdb) bt > > #0 0x285292b7 in pthread_testcancel () from /usr/lib/libpthread.so.2 > > #1 0x285190a2 in sigaction () from /usr/lib/libpthread.so.2 > > #2 0x2851318d in pthread_kill () from /usr/lib/libpthread.so.2 > [...] > > We are using mysql-server-4.1.18_2 from ports with native threads. > > There were some discussions on -current and -stable about this topic. > > See > > http://bugs.mysql.com/bug.php?id=12251 > > for some details. Greg seems to work on it somehow. > > See also > > http://www.krellis.org/unix-stuff/mysql-freebsd-threads.html > > and have a look into > > http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-March/013241.html > > There was some discussion on compiling it with linuxthreads instead > of pthreads. > > -- > MfG/Best regards, Kurt Jaeger 14 years to go ! > LF.net GmbH fon +49 711 90074-23 [email protected] > Ruppmannstr. 27 fax +49 711 90074-33 > D-70565 Stuttgart mob +49 171 3101372 ---------------------------------------------------------------------- Glenn Nielsen [email protected] | /* Spelin donut madder | MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | ---------------------------------------------------------------------- _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-database To unsubscribe, send any mail to "[email protected]"