Bug #42166 | mysql_real_connect() Unhandled exception/Access violation at 0x00000000 | ||
---|---|---|---|
Submitted: | 16 Jan 2009 16:51 | Modified: | 16 Feb 2009 17:25 |
Reporter: | Miguel Cardenas | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: C API (client library) | Severity: | S3 (Non-critical) |
Version: | 6.0.8 | OS: | Windows (Windows XP) |
Assigned to: | CPU Architecture: | Any | |
Tags: | 2008, C++, debug, express, mysql_real_connect, visual |
[16 Jan 2009 16:51]
Miguel Cardenas
[16 Jan 2009 16:59]
MySQL Verification Team
Thank you for the bug report. Why you think is the C API bug and not VS2008 bug? are you tried to debug using for example WinDBG?. Thanks in advance.
[16 Jan 2009 17:15]
Miguel Cardenas
Hi I will try with WinDBG to confirm or discard the possibility that it is MySQL. Don't know WinDBG (am *NIX developer) but will search for it and upgrade this report. I have posted at MySQL mailing list (there got the suggestion to submit the "bug") but got no solution, at VirtualBox to ask if it could cause the create_shared_memory() failure and the MSDN VC++ forum where they said it is my program because thinking it is MySQL is a big assumption and VC++ is okay. In the case that my program runs fine with WinDBG will go back to MSDN and append a note/comment to this bug report clearing it is a VC++ bug and not MySQL. Thanks for your help
[16 Jan 2009 17:25]
MySQL Verification Team
Thank you for the feedback. Reopen this bug report when you have additional info anyway in case you still believe is a C API bug you need to provide a C/C++ code test case. Thanks in advance.
[17 Feb 2009 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".