FAQ
"Run-Time Check Failure #2 - Stack around the variable 'con' was corrupted"

I'm wondering if anyone has gotten this message when running the mysql++ samples. It's occuring when main() exits and the system is trying to release Connection con.

My problems seem to be machine-specific, since I can run the samples (or my own mysql++ programs) on other machines. I just can't figure out why this particular machine is messing up. It was working earlier, and the only thing I can remember doing that made it stop working was building various versions of mysql from the source (but that makes little sense to me).

Specifically, I'm running myql 5.0.0-alpha and mysql++1.7.17 on WinXP, but I'm running into issues on this machine too if I use other combinations of mysql and mysql++. For example, if I'm running mysql 5.0.2-alpha and mysql++ 1.7.25, the MySQL service terminates.

I'm banging my head against the wall! Chuck

Search Discussions

  • Warren Young at Dec 17, 2004 at 7:49 pm

    Chuck Han wrote:

    I'm wondering if anyone has gotten this message when running the
    mysql++ samples. It's occuring when main() exits and the system is
    trying to release Connection con.
    Try simplifying the code to the point that the error goes away. This
    may prove insightful.
    My problems seem to be machine-specific,
    Indeed, it's compiler-specific as well. Keep in mind, MySQL++ is
    cross-platform.
    Specifically, I'm running myql 5.0.0-alpha
    I can't have too much sympathy with your problems since you're running a
    pre-stable version of the database server, especially since you're able
    to crash it. Is there a good reason why you aren't using 4.0 or 4.1?
    combinations of mysql and mysql++. For example, if I'm running mysql
    5.0.2-alpha and mysql++ 1.7.25, the MySQL service terminates.
    I can't imagine a MySQL++ error that could cause MySQL to die. A
    non-buggy version of MySQL should be uncrashable with any conceivable input.
  • Chuck Han at Dec 20, 2004 at 3:02 pm

    Warren Young wrote:

    I'm wondering if anyone has gotten this message when running the
    mysql++ samples. It's occuring when main() exits and the system is
    trying to release Connection con.
    Try simplifying the code to the point that the error goes away. This
    may prove insightful.
    I've isolated it to the release of the Connection object. For example,
    if I change it to Connection*, new it,and DON'T delete it (thus leaking
    it), I experience no exception/crash.
    My problems seem to be machine-specific,
    Indeed, it's compiler-specific as well. Keep in mind, MySQL++ is
    cross-platform.
    I guess I should have been more specific--it is machine-specific in that
    I have the same platform and setup (WinXP, etc.) working successfully
    on several other machines--it's just this one particular computer that
    is giving me trouble.
    Specifically, I'm running myql 5.0.0-alpha
    I can't have too much sympathy with your problems since you're running a
    pre-stable version of the database server, especially since you're able
    to crash it. Is there a good reason why you aren't using 4.0 or 4.1?
    Your lack of sympathy notwithstanding, I should have mentioned that I had
    tried reverting to the production version unsuccessfully (hence retrying
    the example programs) on this one particular computer. My reasons for
    testing against 5.x? Wanting to leverage the new functionality.
    combinations of mysql and mysql++. For example, if I'm running mysql
    5.0.2-alpha and mysql++ 1.7.25, the MySQL service terminates.
    I can't imagine a MySQL++ error that could cause MySQL to die. A
    non-buggy version of MySQL should be uncrashable with any conceivable input.
    I guess I'm looking for someone who has had the same specific problem that I
    have (again, it seems to be a computer-specific WinXP issue, so is it some
    Windows registry thing? is it a Win32 application conflict thing?), not
    someone who cannot imagine/conceive of the problem--I do, however, appreciate
    your first suggestion.
  • Chuck Han at Dec 22, 2004 at 11:09 pm
    I have found my problem:



    In looking at the debug output, I noticed that libmysql.dll was loading
    from the C:\WINDOWS\system32 directory. I don't recall putting the dll
    in that directory, thus I'm thinking that one of my builds of MySQL
    deposited the dll there. It must have been the wrong dll, because when
    I removed it from that directory, everything worked fine.



    Chuck

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupplusplus @
categoriesmysql
postedDec 17, '04 at 5:22p
activeDec 22, '04 at 11:09p
posts4
users2
websitemysql.com
irc#mysql

2 users in discussion

Chuck Han: 3 posts Warren Young: 1 post

People

Translate

site design / logo © 2022 Grokbase