Re: Field_float::val_str crash in 3.23.32

2001-01-25 Thread Sinisa Milivojevic
Kevin Day writes: Description: I'm getting a pretty consistant crash in mysqld: /usr/ports/databases/mysql323-server/work/mysql-3.23.32/sql/mysqld: ready for connections Program received signal SIGSEGV, Segmentation fault. 0x282ae35c in bcopy () from /usr/lib/libc_r.so.4

Re: Field_float::val_str crash in 3.23.32

2001-01-24 Thread Jeremy D. Zawodny
On Wed, Jan 24, 2001 at 03:15:48PM -0600, Kevin Day wrote: Does this only occur when more than one client is accessing the table in question? If so, it's a thread-related problem that has been with us since FreeBSD 3.x. :-( It looks like what I've seen before. I have a re-produceable case that

Re: Field_float::val_str crash in 3.23.32

2001-01-24 Thread Jeremy D. Zawodny
On Wed, Jan 24, 2001 at 05:09:59PM -0600, Kevin Day wrote: I don't know why configure doesn't think I have snprintf, but I guess I'm glad it doesn't, because shouldn't that cause bad things if I did? shouldn't the line be: snprintf(to,val_buffer-length(),"%.*f",dec,nr); In any