-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stack cookie instrumentation code detected a stack-based buffer overrun. in VS2019 #82
Comments
That looks like a more fundamental problem which is likely not related to the shared_components tuple. More information is needed. Are you linking the library (static or dynamic?) against your own application? |
I am linking statically against my own application ( 64 bit )
|
It looks alright. I can't give any additional advice without more information. |
It appears that shared_components is getting initialized multiple times, it crashes on the second initialization. I am still trying to figure out why. |
Hmm interesting... |
I have pushed some changes to |
I have a ton of errors trying to build master regarding the matrix3x3 class
|
If declare the vector3 array operators as constexpr
I get it down to 2 errors:
|
@StellaSmith do you think this is caused by the |
I would've guessed that |
Another thing: Overnight on my part, my bad. |
@RallyTronics let me know if the latest commit changes anything. |
The vector3 array operator [] is still not constexpr so I still get a ton of errors. If I declare those as constexpr it builds correctly. I no longer get the stack-based buffer overrun error. It now crashes in make_rigidbody() here:
I get an exception on the |
|
I get the same exception when running the hello_world example. |
Closing this as the exception I am getting is separate from the original issue. |
I am using version 1.0.0
VS2019 debug build
When the shared_components dynamic initializer ( in shared_comp.h ) executes at startup I get a stack-based buffer overrun exception. Has anyone else run into this?
The text was updated successfully, but these errors were encountered: