I experimented with various things and from what I can tell, the problem
happens when:
1. There is a stored procedure that uses a DECLARE ... CURSOR for SELECT ...
INTO local variables,
2. The table it references "has lots of rows" where lots in this case is
somewhat over 500.
I still would like to upload the stack trace and dump file.
At 07:26 AM 7/31/2004 -0500, rdo mail list address wrote:
>
>Running 5.0.0-alpha-nt on a windows 2000 box.
>
>Upon calling a certain procedure that I created, the server,
>mysqld-nt, errors out and generates a dump.
>
>The procedure references some tables whose descriptions I would prefer not
>to distribute to the list, but would be willing to upload them and the Dr
>Watson log file and user.dmp (35 megabytes dump file) somewhere for
>examination.
>
>How do I make the files available to the proper team?
>
>Thanks.
>
>
>
>--
>MySQL Windows Mailing List
>For list archives: http://lists.mysql.com/win32
>To unsubscribe: http://lists.mysql.com/win32?unsub=1
>
>
