• 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
Vanz

Debug .exe differs from compiled run

5 posts in this topic

Any idea why when I run my program from the vc++ 2008 compiler I'm getting a different output than if I run the .exe from the debug dir. Been working on this program for a couple years and they've always been the same then suddenly they are different. In one version I have an army of guys attacking another army, works fine when ran from the compiler, in the .exe version one entire army does not appear? I can't easily go back to a last saved version (I keep many) as I didn't notice this until about 2 weeks or more of work has been added... I just didn't notice, didn't run this test, was working on menus and other stuff...

 

I've double and triple checked that I am running the same .exe that is being compiled, I purposefully added in an error to one of the buttons, and sure enough they are the same... kinda scratching my head on where to start on this one, my gut feel is that an array is being written beyond it's limit, but since everything works fine in the compiled version kinda hard to debug...

 

Thoughts?

 

Thanks,

 

rhuala

0

Share this post


Link to post
Share on other sites

Yeah, my guess would be something like array overruns or underruns on a stack array or something. I'd suggest:

 

1. See if you can repro it on an optimised build in the debugger.

2. I believe it's possible to attach the msvc debugger to a process that's already running.

3. printf debugging (I guess you'll need to print out to a file)

0

Share this post


Link to post
Share on other sites

2 things I'd check (in addition to the array problem mentioned):

 

1) Check your directory structure. Does the relative directory "../" access the same folder from both your .exe and visual studio project (they can be different).

2) Does the app run alot faster from your .exe than from the project? In this case, are you scaling scene movement by the application speed? If your not then your scene objects may just be moving very far very quickly.

Edited by Nyssa
0

Share this post


Link to post
Share on other sites

This might be caused by variables or objects that are not initialized properly. These kind of bugs can be very hard to find if you do not have a clue where to start.

I'm guessing you are if running the exe from Visual Studio you are running it with the debugger enabled and in debug mode which might cause uninitialized memory to be set to a certain value. Check if the program behaves the same if run from VS without the debugger (CTRL+F5) or if your army goes missing as well.

 

As C0lumbo said, late attaching the debugger might help, as well as some logging.

 

 

I can't easily go back to a last saved version (I keep many) as I didn't notice this until about 2 weeks or more of work has been added... I just didn't notice, didn't run this test, was working on menus and other stuff...

This sounds like you don't use any versioning software like SVN, my advice here is  to start using something to track your changes better. Even if it's only running locally on your machine.

1

Share this post


Link to post
Share on other sites

Yeah, my guess would be something like array overruns or underruns on a stack array or something. I'd suggest:

 

1. See if you can repro it on an optimised build in the debugger.

2. I believe it's possible to attach the msvc debugger to a process that's already running.

3. printf debugging (I guess you'll need to print out to a file)

 

So how do I do #1 and #2? Especially #2

0

Share this post


Link to post
Share on other sites

C0lumbo, on 11 Feb 2013 - 08:53, said:

Yeah, my guess would be something like array overruns or underruns on a stack array or something. I'd suggest:



1. See if you can repro it on an optimised build in the debugger.

2. I believe it's possible to attach the msvc debugger to a process that's already running.

3. printf debugging (I guess you'll need to print out to a file)



So how do I do #1 and #2? Especially #2

 

For #1: Build your solution/project in release mode and start it again from the visual studio. Depending on your configuration the release-mode might be called differntly. Just pick any mode which has no debug-information compiled and code-optimisation enabled.

 

For #2: You can debug any running process from Visual Studio over the menu "Debug" -> "Attach to Process"; However this has some pitfalls as well. See this article here (just the first one that came up on google) or Google it

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