MySQL Bugs: #7380: Server crash using NO_BACKSLASH

Bug #7380	Server crash using NO_BACKSLASH_ESCAPE option
Submitted:	17 Dec 2004 16:37	Modified:	15 Mar 2005 1:10
Reporter:	Ken Johanson	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.2-alpha	OS:	Any (all)
Assigned to:	Jim Winstead	CPU Architecture:	Any

Description:
Using the NO_BACKSLASH_ESCAPE startup option,

(set-variable=sql-mode=PIPES_AS_CONCAT,ANSI_QUOTES,NO_BACKSLASH_ESCAPE)

The query:

select 'te\''st' returns "te''t"

and 

select 'te\'''st' causes a fast server crash:

This was called using the JDBC driver, Statement.executeQuery() which I believe is a pass-through call (no translation)??

How to repeat:
select 'te\'''st';

Dr Watson crashlog

Attachment: mysql-drwtsn32.log (application/octet-stream, text), 26.65 KiB.

Using the command line client on linux i was able to crash the server
using the 2nd query:

  mysql> select 'te\'''st';
  ERROR 2013 (HY000): Lost connection to MySQL server during query

The first one i could only reproduce in the following form:

  mysql> select 'te\''st';';                                                              
  +-------+
  | te''t |
  +-------+
  | te''t | 
  +-------+
  1 row in set (0,00 sec)

  ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''' at line 1

I assume that the additional '; was only needed for the mysql clients input parser

Sorry, I only included the first example to illustrate that the intended non-backslash behavior was working as expected. This bug relates more to example two; one may only be a clue to the crash / parsing problem. 

I only included the ';' out of habit; in the actual use-case I dont use the semi-colon, but did still get the crash.

This looks like it was fixed along with bug 6368, which will be fixed in 5.0.3.

yes, this seems fixed with 5.0.3. Awesome!!!!!