• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
belfegor

Strange bug in Release mode

15 posts in this topic

I am using VS2012. I have a bug in my code that i don't know how to overcome as it appears in bizarre situation. It works fine in Debug but crashes in Release mode.

 

I have  a class with couple of vectors and some pointers:

[code]class Foo { private:     Bla*                       pBla;        std::vector<shared_ptr<Node>> vBar1;      std::vector<shared_ptr<Node>> vBar2;      std::vector<shared_ptr<Node>> vBar3;      //std::vector<shared_ptr<Node>> vBar4; ... more data public: ... };[/code]

 

When i introduced one more vector (vBar4) to this class it crashes my app even if don't use it anywhere, if i comment it then everything works.

 

WTF is going on?

 

Thank you for your time.

0

Share this post


Link to post
Share on other sites

[quote]

We need to see code before we can try to debug it.

[/quote]

 

I think there is no need for more code because even if i just add vector declaration (and nothing else) it just crashes my app in Release build, comment it and everything works.

0

Share this post


Link to post
Share on other sites
I haven't used C++ on VS2012, only C#, but maybe solutions are handled the same way.

Are you using two or more projects in your solution, where one project contains node and the other one, the code your showing? If yes, check compilation options for those projects.

I recently had the same issue at work. Two projects set to "Any CPU" mode and one goes for "x86". Switching it to "Any CPU" didn't help either, so i usually switch all projects to x84 and make sure they are built on compilation Edited by Sollum
1

Share this post


Link to post
Share on other sites
I think there is no need for more code because even if i just add vector declaration (and nothing else) it just crashes my app in Release build, comment it and everything works.

 

I have recently seen some weird things happen when I use templates in VS2012. Have your tried to "Clean" up the .obj files and do a full rebuild of the project?

1

Share this post


Link to post
Share on other sites
When i introduced one more vector (vBar4) to this class it crashes my app even if don't use it anywhere, if i comment it then everything works.

WTF is going on?
Memory corruption is your best bet.

Try compiling your release mode with debugging symbols, and examine where the application crashes in release mode.

EDIT:
As simast suggested, try rebuilding your project before assuming memory corruption. Edited by fastcall22
1

Share this post


Link to post
Share on other sites

I'm not 100% certain, but maybe the clean/rebuild just moved the memory around and hid the bug, but did not fix it. I would take a look at every place you use the pBla variable. Make sure it's initialized at null, set back to null when deleted and always check for != null before using it. Also check static array before/after the places where you use your Foo class, because it might be a buffer overflow, it cause this kind of problems.

2

Share this post


Link to post
Share on other sites
I'm not 100% certain, but maybe the clean/rebuild just moved the memory around and hid the bug, but did not fix it. I would take a look at every place you use the pBla variable. Make sure it's initialized at null, set back to null when deleted and always check for != null before using it. Also check static array before/after the places where you use your Foo class, because it might be a buffer overflow, it cause this kind of problems.

 

Yup.

 

If it wasn't just a build error.

 

Adding a vector is not a bug unless you type it in wrong, but it can cause an existing bug to crash the program or give you heisenbergs.

0

Share this post


Link to post
Share on other sites

If i'm not mistaken, i believe it's actually because you don't use the vector.

Being in release mode you are not permitted to declare variables/methods without actually using them.

-3

Share this post


Link to post
Share on other sites
If i'm not mistaken, i believe it's actually because you don't use the vector.

Being in release mode you are not permitted to declare variables/methods without actually using them.

That's just... wrong. You're absolutely allowed to have variables and methods that you never use. The compiler is free to remove them (to some degree), but merely having them itself is not an error in any way.

1

Share this post


Link to post
Share on other sites
If i'm not mistaken, i believe it's actually because you don't use the vector.

Being in release mode you are not permitted to declare variables/methods without actually using them.

That's just... wrong. You're absolutely allowed to have variables and methods that you never use. The compiler is free to remove them (to some degree), but merely having them itself is not an error in any way.

In most languages, at least. In Go, for instance, declaring unused variables is an error. But for C++, you can of course declare placeholder variables which you aren't actually using yet, the compiler will simply ignore them (usually). At least with correct code, adding extra unused variables should not change the program's observable behaviour.

0

Share this post


Link to post
Share on other sites
If i'm not mistaken, i believe it's actually because you don't use the vector.

Being in release mode you are not permitted to declare variables/methods without actually using them.

That's just... wrong. You're absolutely allowed to have variables and methods that you never use. The compiler is free to remove them (to some degree), but merely having them itself is not an error in any way.

In most languages, at least. In Go, for instance, declaring unused variables is an error. But for C++, you can of course declare placeholder variables which you aren't actually using yet, the compiler will simply ignore them (usually). At least with correct code, adding extra unused variables should not change the program's observable behaviour.

 

So long as their construction/destruction has no global side-effects.

Edited by Ameise
0

Share this post


Link to post
Share on other sites

The last time Ive had a bug like this it was becasuse the debug mode did additional things like initializing variables to NULL. ....in debug mode everything was fine but in "normal" mode it produced a weird error.

0

Share this post


Link to post
Share on other sites

Clean and Rebuild may have worked because the dependent library, that is associated with the class, might be built previously in debug mode, and since you just switched to Release and rebuilt, it might not have been picked up appropriately. For Release builds, all the dependencies should also be built in release mode, otherwise it won't work.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0