MySQL Bugs: #13606: Access Violation crash after creating a function and push button refresh

Bug #13606	Access Violation crash after creating a function and push button refresh
Submitted:	29 Sep 2005 12:59	Modified:	4 Oct 2005 8:22
Reporter:	Adrian Spinetta	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Administrator	Severity:	S1 (Critical)
Version:	5.0.13 rc	OS:	Windows (windows 2000 sp4)
Assigned to:	Vladimir Kolesnikov	CPU Architecture:	Any

Description:
After creating a function, if threre is a syntax error, it shows "error access violation", after that, any attempt of using refresh or selecting another schema causes the server crash.

How to repeat:
Select view-catalogs, use a schema, tab stored procedure,button create stored proc,button create function.
Write this function:
 create function schema.getexpe (e char(23) ) returns char(28) 
  begin
   return substr(e,1,3) || substr(e,15,3);
  end

This goes right, but if there is a syntax error it crash the server.

I got the access violation when creating and every time I click
the refresh button however without to crash the server, could
you please provide your my.ini and which server binary are
you using.

Thanks in advance.

the server is mysqld-nt

here is the my.ini:
[mysqld]
port=3306
basedir="C:/My5/"
datadir="C:/My5/Data/"
default-character-set=latin1
default-storage-engine=INNODB
max_connections=100
query_cache_size=0
table_cache=256
tmp_table_size=5M
thread_cache_size=8
myisam_max_sort_file_size=100G
myisam_max_extra_sort_file_size=100G
myisam_sort_buffer_size=8M
key_buffer_size=8M
read_buffer_size=64K
read_rnd_buffer_size=256K
sort_buffer_size=212K
innodb_additional_mem_pool_size=2M
innodb_flush_log_at_trx_commit=1
innodb_log_buffer_size=1M
innodb_buffer_pool_size=8M
innodb_log_file_size=10M
innodb_thread_concurrency=8

I got only the Access Violation from MA but not the server crash.

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Additional info:

I cannot repro neither server crash nor AV in MA. Please give the exact steps to reproduce.