Bug #6456 Access violation using Tab in Edit mode

• Submitted: 5 Nov 2004 9:44
• Modified: 15 Nov 2004 9:53
• Reporter: Chris Munasinha
• Status: Closed
• Category: MySQL Query Browser
• Severity: S3 (Non-critical)
• Version: 1.1.0 Gamma
• OS: Windows (Win2K SP4)
• Assigned to: Mike Lischke
• CPU Architecture: Any

[5 Nov 2004 9:44] Chris Munasinha

Description:
Using the Tab key to move between cells in Edit mode on a newly fetched resultset (when adding a new row) causes an access violation message to appear in the status bar. The active cell doesn't move and another new row appears below it, but only the first time. The message is "Access violation at address 004054D4 in Module 'MySQLQueryBrowser.exe'. Read of address 00000008'."

How to repeat:
- Fetch a new resultset (SELECT * FROM etc)
- Select Edit Mode
- Double Click on a cell on the last row to insert a new row.
- Enter some information in and press the Tab key

[5 Nov 2004 9:54] MySQL Verification Team

Hi,

Thank you for the report, but I can't repeat it.
These are exact actions to reproduce the problem?

[5 Nov 2004 10:02] Chris Munasinha

Yep. I did a select, clicked edit, double clicked on any cell on the last row, entered a couple of letters in (its a varchar field), pressed Tab and it gave me the access violation message in the statusbar. I can attach a screenshot or something if it helps?

[5 Nov 2004 10:16] MySQL Verification Team

I still can't repeat it.
Can you reproduce it on any table? If no, please send me a table structure.

[5 Nov 2004 10:22] Chris Munasinha

It happens on any table including empty ones. I'll attach a create to this bug report.

[5 Nov 2004 10:27] Chris Munasinha

Create SQL for test case

Attachment: bug.txt (text/plain), 419 bytes.

[5 Nov 2004 10:27] Chris Munasinha

Screenshot of access violation

Attachment: bug.jpg (image/pjpeg, text), 60.23 KiB.

[5 Nov 2004 16:16] Mike Lischke

We cannot reproduce this problem with the current build, so it seems we have fixed that internally already. Please wait for the next release to see if it is also fixed for you. If you urgently need a solution you can always get the latest source snapshot from the repository.

[15 Nov 2004 9:13] Chris Munasinha

I can confirm that the bug has gone in 1.1.1 Gamma.

[15 Nov 2004 9:52] Mike Lischke

Hi Chris, that is great news. Thank you for your confirmation.

Mike