InvalidRequestException not found in debug dll!

[Crash]

I downloaded the 0.6.0 SDK.
In release mode everything works fine. However, in debug mode I get the error:
The procedure entry point InvalidRequestException(...) could not be found in the DLL "CEGUIBase_d.dll".

I searched for any old CEGUI files on my hard drive but didn't find any, so i think the correct header and library files are used. What I find weird is that I get the error only in debug mode, not in release mode.
I then downloaded the 0.6 svn repo and got the same error

[CrazyEddie]

Hi,

Sorry to hear about your woes.

It does definitely sound like there is something (lib / dll mismatch probably) being used from an old version. The only thing I can suggest is to have another look for older files - especially for libs in directories referenced in the MSVC lib search paths, and dlls in the main executable path.

Nothing else should cause this issue, so I'm unable to offer any additional ideas.

CE.

[Crash]

I looked for old CEGUI files but DEFINITELY didn't find any. Does this error maybe have something to do with this macro?

Code: Select all

    \remarks
    There's a bug in Visual Studio 7.1 (see http://support.microsoft.com/kb/199057/en)
    and lower which leads to incorrect __LINE__ macro expansion if used inside a
    function and compiled with "Program Database for Edit & Continue" (/ZI) where
    instead of a constant expressing line number you'll get the
    following: (__LINE__Var+constant). The workaround consists in using compiler
    option "Program Database" (/Zi) instead
    --> Project Properties\C/C++\General\Debug Information Format\Program Database (/Zi).
    Visual Studio 2005 corrects the problem. Premake files were
    modified to contemplate this for VS2002 and VS2003.
    */
    #define InvalidRequestException(message)  \
        InvalidRequestException(message, __FILE__, __LINE__)


Here's a screen of the error message:


I'm wondering why there is only one "String" in the error message because the constructor of InvalidRequestException has more than one string as an argument. The macro however has exactly one string as an argument.
By the way: I'm using Microsoft Visual C++ 2008 Express

[ApostropheST]

I want to second this issue.

I used CEGUI 0.5.0 in a previous test bed. I'm using the exact same CEGUI-related code in a new app, only in this app, the libs, includes, and dlls are 0.6.0.

I'm using MSVC++ 2005 Express and getting the exact same error message (though in English ).

All of the libs, headers, and dlls came straight out of the SDK zip file, so I'm not sure that a mismatch is at fault. The timestamps for the files I checked are all consistent with those in the SDK zip for 0.6.0.

Not sure what else to say about it.

[CrazyEddie]

Hi,

Are both of you guys using MSVC++ 2005? If so, do you both have SP1 applied? If not, that could be related to the issue - even if it's not related to this issue, without the MSVC++ 2005 SP1 version you'd have other issues down the line.

This is the only other thing that has come to mind so far.

CE.

[scriptkid]

Hi,

when do you get this error? When you run a sample, or when your run your own code? If it's your own code, can you try if you can build the Cegui samples and run one?

[Jmiller]

I'm getting the same errors. I've linked all the proper .dll / .lib / .h files from version 0.6.0 and I'm using MSVS C++ 2005 with SP2 installed. I'm trying to run example 7 from ogre's tutorial section. I've even tried putting back the old files that ogre came with. This problem happens when I try to run the application in debug or release.

[CrazyEddie]

Hi,

I just briefly checked at MSDN and could find no reference to a SP2 for Visual Studio 2005. If you could clarify / confirm what you mean by that reference it would be great. Perhaps it is possible there are compatibility issues between SP2 / SP1 builds the same as there are for SP1 / No SP builds?

With reference to the ogre parts... Did you re-build the Ogre GUI Renderer when you updated to 0.6.0? This is essential, since the renderer must be built against the same version of the library that the 'main' parts of the application are using.

CE.

[Jmiller]

I misunderstood what SP you were talking about, I was referring to SP2 of windows when I said that which means nothing to ogre and cegui i guess. Anyways, I was able to make some progress. I had read certain posts here and there about recompiling CEGUI and Ogre's renderer but it seemed to be unclear of how to do it at first glance. I'll try to explain in detail what I did and hopefully it will help others that were in my situation.

First I downloaded CEGUI's source files. At first I didn't know what to do with it until I read the FAQ. In the make folder there is a .bat file for the appropriate version of visual studio you use (2003, 2005, 2008). Run that and it will generate your solution and project files. Now you should download the dependencies files and copy the dependencies folder to the main CEGUI-0.6.0 folder. You should then open the solution and attempt to compile. If it doesn't work you may need to do some extra footwork to link the .lib's and include folders. Find the .lib / .dll files that have just been created and move those to their respective folders that Ogre is looking for them in. Now try to recompile the Ogre renderer project and you should get rid of these errors. At this point I was able to get it to work in debug mode, but not release. I'm sure there's something that I missed in my efforts, but it's a start. Hope this can help.