AutoCAD 2013 custom object stack corruption (migrating from 2012)

[Anonymous]

Hello!

I have a problem with my custom object in AutoCAD 2013 and I haven't been able to track down the source of the problem yet.

In my custom object I get run-time check failures (stack corruption around a local variable) when trying to return to a calling method. I'm using ObjectARX with C++. The problem does not occur in AutoCAD 2012 and prior versions. Does anybody know or at least have a faint idea what changed in AutoCAD 2013 that might be causing this?

Any form of help will be appreciated.

[loic.jourdan]

simple guess

What is the type of your local variable?

It may crash in its destructor.

I hope it helps

[Anonymous]

Thank you for your answer.

I already looked into that, but that doesn't seem to be the problem.

What really confuses me is the fact that it only happens in 2013 and 2014, but not in the previous versions.

[kubitTilo]

Maybe you've messed up some project settings during migration to ObjectARX 2013 (and VC++10).

Have you already checked that you are linking against Multihreaded-DLL runtime and have not defined _DEBUG preprocessor symbol?

[Anonymous]

Thanks for your answer.

That's not the problem either, I checked 😞

[kubitTilo]

Are you linking with 3rd party libraries (that are using other flavours of MSVC runtime)?

[owenwengerd]

There's really no way to guess. I would post the problem code to see if someone can spot the bug.