vieten / sequel-pro

Automatically exported from code.google.com/p/sequel-pro
Other
0 stars 0 forks source link

Sequel Pro crashes when connection to MySQL 4.1.14-nt on Windows XP #1181

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Enter connection information (connecting as root, no pwd, no SSL)
2. Connect to MySQL 4.1.14-nt on Windows (part of a XAMPP distribution)
3. Crash window appears immediately after pressing "Connect":
-[NSNull length]: unrecognized selector sent to instance 0x7fff7df60e00

What is the expected output? What do you see instead?
As stated above. 

What version of Sequel Pro are you using? What version of MySQL are you
connecting to on the server?
SequelPro 0.9.9.1 Build 3408
MySQL 4.1.14-nt (part of a XAMPP installation.

Please provide any additional information below.
I can connect to this database with SequelPro 0.9.8.1, Build 2492

Original issue reported on code.google.com by michael....@gmail.com on 9 Sep 2011 at 5:15

GoogleCodeExporter commented 9 years ago
I believe I've fixed this in r3424.  You can confirm this by downloading a 
development version, which we make available from http://nightly.sequelpro.com/ 
- although we don't recommend their use with production systems, just in case.

Many thanks for the report - we'd seen the crash logs, but this helped track it 
down :)

Original comment by rowanb@gmail.com on 12 Sep 2011 at 9:40

GoogleCodeExporter commented 9 years ago
I'm having same problem with 0.9.9.1

I tried r3452 and it's also crashing

Original comment by jorfe...@gmail.com on 21 Dec 2011 at 9:26

GoogleCodeExporter commented 9 years ago
Hi jorfermo,

Could you submit a crash report with that email address, or mention "1181" in 
the comment box, so I can pull out the linked crashes?  Then post an update 
here, and I'll take a closer look.

Thanks!

Original comment by rowanb@gmail.com on 2 Jan 2012 at 12:59

GoogleCodeExporter commented 9 years ago

Original comment by mattlangtree on 14 Jan 2012 at 8:55

GoogleCodeExporter commented 9 years ago
I'm going to mark this as closed for now, as we've rewritten that part of the 
MySQL framework so this should no longer occur.  But do let us know if it still 
occurs in 1.0/recent nightlies!

Original comment by rowanb@gmail.com on 17 Dec 2012 at 11:17