MySQL Bugs: #8694: "Access Violation" when trying to Edit table.

Bug #8694	"Access Violation" when trying to Edit table.
Submitted:	22 Feb 2005 16:29	Modified:	1 Apr 2005 19:01
Reporter:	Matthew Connor	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S1 (Critical)
Version:	1.0.19	OS:	Windows (Windows 2000 5.00.2195 SP4)
Assigned to:	Michael G. Zinner	CPU Architecture:	Any

Description:
Attempting to edit a table consistently produces the error:

Access violation at address 0032C1B0 in module 'libmysqlx.dll'. Read of address 00000000

How to repeat:
1) Run MySQLAdministrator.exe.
2) Connect to server.
3) Double click on "Catalogs".
4) Double click on a database containing at least one table.
5) Double click OR right click and select "Edit" on a table.

NOTE: Same error occurs in Query Browser when right clicking on a table and selecting "Edit".

Suggested fix:
Unknown.

Following reproduction steps using MySQL Administrator under Linux 2.4.21-15.0.3.ELsmp poduces fatal error as well:

mysql-administrator: line 9: 891 Segmentation fault

I wasn't able to repeat either Windows or Slackware Linux.

When I first installed and setup this database (yesterday), I was able to create and and edit the table. Now I cannot. I've got to do something...I can't even work with the table at all. Any ideas of how I can get around this?

Maybe I am missing some steps before apply the ones you reported
or environment differences.

What information could I provide that may help? Also, I just deleted the table in question successfully and recreated it. When I create a new table, it allows me to define all the columns and apply the changes with no problems...but when I try to EDIT that table, it crashes with the same message I sent above.

I will put the output of the command: 

strace -f -tt -T -v -o trace.tmp mysql-administrator

in the files section. Hope that helps.

I took a look at the trace output which I have uploaded...I'm seeing a lot of errors that say "Resource temporarily unavailable". I'm going to check the process limits in /etc/security/limits.conf to make sure mysql can fork when needed. I'll let you know if increasing the limit resolves the issue.

Increasing the process count limit did not seem to change anything. Does that trace tell you anything useful? Much of it is greek to me.

Miguel, I understand that you cannot repeat the problem I'm having, but are you still looking into it or have you considered the case closed? Just curious. Also, I'm very much hoping you can tell me what this means. I created an identicle database on another SQL server to the one I'm having difficulty with. I can edit it via the Administrator with no problem. I sniffed the information the MySQL server is returning for both the working database and the one that causes Administrator to crash. When clicking "Edit" on a table, the Administrator issues the command to the server:

SHOW FULL COLUMNS FROM `logging`.`ftp`

The data that comes back from the server from that command is obviously binary, but there is some readable text. The WORKING server sends back some of the following readable text:

---BEGIN VALID SERVER REPLY---
Field @              
Type (              
Null                
Key                
Default @              
Extra               
Privileges P            
>    
id int(10) unsigned  PRI  auto_increment select,insert,update?    eventtime datetime   0000-00-00 00:00:00  select,insert,update
---END VALID SERVER REPLY---

The server causing the Administrator to crash sends back the some of the following readable text. This is curious as it almost looks like source code...

---BEGIN INVALID SERVER REPLY---
def  #sql_6b0_0 /tmp/#sql_6b0_0 Field COLUMN_NAME !           >    
def  #sql_6b0_0 /tmp/#sql_6b0_0 Type COLUMN_TYPE !           F    
def  #sql_6b0_0 /tmp/#sql_6b0_0 Collation COLLATION_NAME ! x         >    
def  #sql_6b0_0 /tmp/#sql_6b0_0 Null IS_NULLABLE !           <    
def  #sql_6b0_0 /tmp/#sql_6b0_0 Key COLUMN_KEY !           D    
def  #sql_6b0_0 /tmp/#sql_6b0_0 
default COLUMN_
defAULT !           9    
def  #sql_6b0_0 /tmp/#sql_6b0_0 Extra EXTRA ! <         C    
def  #sql_6b0_0 /tmp/#sql_6b0_0 Privileges PRIVILEGES !           D    
def  #sql_6b0_0 /tmp/#sql_6b0_0 Comment COLUMN_COMMENT !                K    

id int(10) unsigned   PRI  auto_increment select,insert,update,references 9    eventtime datetime      select,insert,update,references        "
---END INVALID SERVER REPLY---

Does that look familiar to you? I'm guessing the Administrator is crashing because it's not expecting that type of data. Any thoughts at all?

See Bug #8335...user's complaint is identicle to mine.

Hi Matthew,

Notice that the issue in #8335 isn't with MySQL Administrator instead
is with the 5.0.2 server which crashes when connected via MA or is
executed some specific commands like desc table_name. It is this
your case ?

Maybe we're looking at two different things...Bug #8335 is concerning MySQL Administrator under Windows. The description of Bug #8335 is as follows:

When trying to edit a table running on a 5.0.2-alpha server (Linux or Windows),
the following error message appears:

MySQL Administrator Exception - Access violation at address 0034C1B0 in module
'libmysqlx.dll'. Read of address 00000000

After pressing OK, it's impossible to edit the table.

This doesn't happen when editing tables running on 3.x or 4.x servers.

I'm not sure if this matters, but I'm running an italian version of Windows XP
Professional.

Downgrading to MySQL Server 5.0.1 has resolved this issue. It no longer causes the client programs to crash. I guess this will be looked into for 5.0.3?

Yes 5.0.3 will fix this issue.

Changed status for not a bug since is related to the bug #6950.

Showing issue reported with Access violation..message

Attachment: access-violation.PNG (image/png, text), 110.48 KiB.

Testing now with 5.0.3 server build from source I was able to
repeat the behavior reported.
I attached a picture showing the message screen error.

Just found this bug to be still present in server 5.0.3 beta. Both when using table editor in Query browser 1.1.6 and in Administrator 1.0.19.

Hi all,
from reading elsewhere, and my own reproduction, this error only occurs if the table contains an INTEGER (also smallint/bigint) data field.

I can confirm that this still happens under 5.0.3 beta, with Admin 1.0.19.

I haven't noted that this was reported fixed in any of the change logs since 5.0.1

Cheers.

so, i´ve testet with 5.0.1 and 5.0.3 database server and this present the same problem, but whit the table SCHEMATA in informacion_schema database i can edit the table. please sendme a email sistemas@metricom-col.com

This issue has now been fixed and will be in the next releases of MA & QB.

As this is a major issue I have uploaded intermediate builds that include the fix to the following FTP address.

ftp://ftp.mysql.com/pub/mysql/download/mysql-administrator-1.0.20-win.msi
ftp://ftp.mysql.com/pub/mysql/download/mysql-query-browser-1.1.7-win.msi

The official releases will follow early next week.