Is there a way to get better information for the context of an error when using msvc? (ex: C2248)

Question

Hi,

I'm wondering if there is a way to get better information about the location of an error in msvc (2005)?

Exemple, when inheriting from boost::noncopyable in my class I get a C2248 error saying something like:

error C2248: 'boost::noncopyable_::noncopyable::noncopyable' : cannot access private member declared in class 'boost::noncopyable_::noncopyable'. This diagnostic occurred in the compiler generated function 'MyClass::MyClass(const MyClass &)'

but it fail to tell me where exactly the copy constructor was called. This is a little annoying. I'm really not sure but I think I remember seeing a settings somewhere where I could specify the output level or something but I searched and found nothing so my question is: Is there a way to get better (fuller?) error message in msvc?

Edit: Well since stackoverflow just told me I should look to accept an answer, I was wondering if anyone could tell if msvc 2008/2010 give a better diagnostic for this error? Someone also mentioned GCC should do, can anyone confirm this? What about other compilers (Intel?, Comeau?)

Thanks

Answer 1

In the output window or the build log you should see where the compiler tried to use the template in your code... you have to scroll around a bit though.

If there is not enough information in the build logs, there is also an option controlling msbuild verbosity:
Tools->Options->Projects and Solutions->Build and Run->MSBuild project output verbosity

Answer 2

You could temporarily create a manual copy constructor (with the same signature) and the default implementation, just for the purpose of tracking down this error..? Not sure if that would make it any easier to find.

Answer 3

Open the output window, where the full building log is displayed. Check there the error message. Under that error message, you can usually find more information that can help you trace the source of the problem.

If you double click the problem in the error list and the go to the output window, the cursor will be positioned to that error message.

Answer 4

I can confirm with Code::Blocks and VC++ 2005, that it gives no hint where the error occurs. Neither does declaring your own private copy constructor help.

#include <boost/noncopyable.hpp>

class X: boost::noncopyable
{
};

void foo(X x) {}

int main()
{

    X x;
    foo(x);
}

The compile log (line five is the last line of the class declaration):

main.cpp(5) : error C2248: 'boost::noncopyable_::noncopyable::noncopyable' : cannot access private member declared in class 'boost::noncopyable_::noncopyable' C:\boost_1_38_0\boost/noncopyable.hpp(27) : see declaration of 'boost::noncopyable_::noncopyable::noncopyable' C:\boost_1_38_0\boost/noncopyable.hpp(22) : see declaration of 'boost::noncopyable_::noncopyable' This diagnostic occurred in the compiler generated function 'X::X(const X &)'

Unless there's a compiler switch to enable more thorough error diagnostics, this wouldn't be the first time for me to simply compile the file with GCC (MinGW) to get more helpful error diagnostics. (Alas, your code should be free of VC++ extensions.)

Answer 5

I've never tried to make it work inside of Visual Studio, but if you don't mind compiling from the command line, STLFilt, from Brain Damaged Software, can be quite helpful.

For those who've been around a while, and think BDS sounds a bit familiar, yes, this is the same company (or guy, really -- Leor Zolman) who wrote BDS C, one of the first C compilers for CP/M.

Edit: Looking at the site, it appears that filtering in the IDE does now work.