I have a similar problem with a list of union(s) (see my email, one
hour before yours).
It seems there is something in the way mysql parses the string
that makes it crash. I tried with version 4.1.2 as well, but
it keeps on crashing.

> -----Messaggio originale-----
> Da: Chambon [mailto:[EMAIL PROTECTED]
> Inviato: lunedi 14 giugno 2004 16.49
> A: [EMAIL PROTECTED]
> Oggetto: query string make mysqld crash (mysqld 4.0.20)
>
>
> Hi,
>
> Using Mysql 4.0.20-standard-log since a few days
> I encontred an error that I had never seen before.
>
> Here is what I have done :
>
> 1_ create an innodb table :
>
>     create table Test (JobStatus varchar(32) ) type = innodb;
>
> 2_ Run the following request :
>
>     select JobStatus from Test where
>
> ((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((
> (((((((((((((((((((((((
>       JobStatus = 'xyz'
>
> ))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))
> )))))))))))))))))))))))
>      ;
>
>
>     This imply a  mysqld crash (and restart) each time I run the request !
>     I encontred this problem with  4.0.20-standard-log running on
> Solaris 8
>     and on Solaris 9.
>
>     If I made a try on the previous version I used (4.0.13, on Solaris 8)
>     everything work fine.
>     If I decrease the number of parenthesis to 2 * 88, It run
>     If I increase the number of parenthesis to higher than 2 * 88
> mysqld crash
>
>     Is there a bug on 4.0.20 ? or do I miss-configure a variable ?
>
>     In a hostname.err we find :
>
>      > mysqld got signal 11;
>      > This could be because you hit a bug. It is also possible
> that this binary
>      > or one of the libraries it was linked against is corrupt,
> improperly built,
>      > or misconfigured. This error can also be caused by
> malfunctioning hardware.
>      > We will try our best to scrape up some info that will
> hopefully help diagnose
>      > the problem, but since we have already crashed, something
> is definitely wrong
>      > and this may fail.
>      >
>      > key_buffer_size=67108864
>      > read_buffer_size=1044480
>      > max_used_connections=0
>      > max_connections=128
>      > threads_connected=1
>      > It is possible that mysqld could use up to
>      > key_buffer_size + (read_buffer_size +
> sort_buffer_size)*max_connections = 1506815 K
>      > bytes of memory
>      > Hope that's ok; if not, decrease some variables in the equation.
>      >
>      > -e
>      > Number of processes running now: 0
>      > 040614 13:33:33  mysqld restarted
>      >
>
> Thans for any help
> Regards
>
>
> --
> Bernard CHAMBON
> IN2P3 / CNRS (Centre de Calcul de LYON)
> email:        mailto:[EMAIL PROTECTED]
> Tel :         04 72 69 42 18
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to