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

Automatic code insertion with VC++

7 posts in this topic

Is there any to get Visual C++ 2003 to automatically insert a piece of code at the start of every function? Ideally this would happen before the preprocessor runs and will not make any changes to the code files (much like macro replacement) and could be enabled/disabled per build configuration.
0

Share this post


Link to post
Share on other sites
If I understand what you are asking, then no. Why not just use a macro?
0

Share this post


Link to post
Share on other sites
In MSDevStudio you can use the /Gh option to insert a call to _penter at the start of every function. You can also do /GH to add a call to _pexit at the end of every function. Look up the references for the compiler options for more info.

Skizz
0

Share this post


Link to post
Share on other sites
I didn't want to use a macro because that would require me to explicitly call the macro at the start of every function.

_penter and _pexit won't work either, because I'm trying to access the __FILE__, __FUNCTION__ and __LINE__ macros at the start of every function.


What I'm really want to do is this:


class FuncTracker
{
public:
FuncTracker(const std::string& name):_name(name)
{
f << "entering: " << _name <<std::endl;
}

~FuncTracker()
{
f << "leaving: " << _name <<std::endl;
}

std::string _name;


static file f;
}



Then in every function:



void f()
{
FuncTracker _funcTracker;//I want this line to be inserted in every function
}



Obviouslyonce this is working it can be expanded to do useful work.
0

Share this post


Link to post
Share on other sites
Ah, that's not so easy. It's doable using the _penter/_pexit methods - you will need to get the function address (in EIP register) and compare it against addresses in the map file that can be generated by the linker (assuming no rebasing has occurred). It'll be very slow though.

The only other way is to use macros. You can make this a bit easier on yourself and more robust by using the following:

class ExecutionTracker
{
private:
ExecutionTracker(void);
public:
ExecutionTracker(char *function, char *file, int line) :
m_func (function),
m_file (file),
m_line (line)
{
cout << "Entering " << m_func << ", " << m_file << ":" << m_line << endl;
}

~ExecutionTracker (void)
{
cout << "Exiting " << m_func << ", " << m_file << ":" << m_line << endl;
}
private:
char
*m_func,
*m_file;

int
m_line;
};

#define TRACKER ExecutionTracker track (__FUNCTION__, __FILE__, __LINE__);

void main (int argc, char *argv [])
{
TRACKER;

// code....
}

which only requires one macro per function and neatly copes with multiple exits.

Skizz

0

Share this post


Link to post
Share on other sites
This has been bugging me for awhile as well.

It has to be possible, even if it requires some elementary source pre-processing before being compiled by cl.exe. It is irritating that this capability is such a pain in the ass to orchestrate, because both of the pieces of the puzzle are sitting right in front of us: the __FUNCTION__ macro, and _penter/_pexit. However, the two just don't work with one another unless we want to annotate each and every function with ugly macros.

The question becomes: how difficult would it be to correctly parse out the beginning of a C++ function from a source file? If it isn't terrible, then injection becomes trivial.
0

Share this post


Link to post
Share on other sites
It's exactly what _penter and _pexit are for. You won't be able to use any user-friendly macros, but you will be able to examine the stack, and figure out the function and file and line number from the debugging information.
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