visual-c++-2008

How do I view the compiler-generated mangled names for overloaded functions in C++? I'm using VC9 but answers for other compilers are welcome too. Edit: I find all the answers useful here. Accepting the one I liked best. You could look in the map file. Assuming you have map file generation turned on. You can see the decorated function names by using Dependency Walker . Open any DLL\EXE in dependency walker and in right pane you can see a list of decorated function names. Since you also ask about other compilers. There is a tool called nm on the gnu toolchain. You will get it on linux and

I'm trying to debug a problem in a DLL written in C that keeps causing access violations. I'm using Visual C++ 2008, but the code is straight C. I'm used to Delphi, where if an exception occurs while running under the debugger, the program will immediately break to the debugger and it will give you a chance to examine the program state. In Visual C++, though, all I get is a message in the Output tab: First-chance exception at blah blah blah: Access violation reading location 0x04410000. No breaks, nothing. It just goes and unwinds the stack until it's back in my Delphi EXE, which recognizes

This question is related to "How to make consistent dll binaries across VS versions ?" We have applications and DLLs built with VC6 and a new application built with VC9. The VC9-app has to use DLLs compiled with VC6, most of which are written in C and one in C++. The C++ lib is problematic due to name decoration/mangling issues. Compiling everything with VC9 is currently not an option as there appear to be some side effects. Resolving these would be quite time consuming. I can modify the C++ library, however it must be compiled with VC6. The C++ lib is essentially an OO-wrapper for another C

STL containers require the stored values to be copy constructible and assignable. const T is obviously not an assignable type for any T, but I tried to use it (just being curious) and found out that it compiles and, moreover, behaves as an assignable type. vector<const int> v(1); v[0] = 17; This successfully runs in Visual Studio 2008 and assigns v[0] to 17. This is not a bug in the implementation as others have suggested. Violating the requirements of a C++ Standard Library facility does not render your program ill-formed, it yields undefined behavior. You have violated the requirement that

I'm using CUDA (VC++, Visual studio 2008sp1) to debug a FEM program. The program can only run on a Win32 platform, for the insufficiency of cuda. I think the library files linked are all compiled on the x86 platform, but when I compile it, I get the error message "fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'X86'". I have tried to convert the platform to x64, but it didn't work. Please tell me: what is "module machine type" and what is "target machine type"? How can I overcome it? C Johnson I wrote a blog entry about this, as I encountered this maddening