[BloodyMess1.5.4] cannot debug NxOgre

I am running the BloodyCake, but find I cannot debug NxOgre. Here are some details:
1. Unzip BloodyMess and BloodyCake to same folder.
2. Compile BloodyMess and BloodyCake in debug mode. There are not any compiling problems. I am using VS2005 SP1.
3. Press F5 to run BloodyCake, it stops at:
> NxOgre_Debug.dll!NxOgre::World::precreateSingletons() Line 71 C++
And an error message shows up: "There is no source code available for the current location."
4. If I press F5 again, the program can continue. If I start the program with Ctrl+F5, I will not meet this problem.

So, seems some debug infomation is missed in NxOgre_debug.dll, is it the expected behavior?

有个生成后事件报错
我一直都不管
其实已经编译通过了

There is a generation after the events of error
I have always been regardless of
In fact, has been compiled through the

有个生成后事件报错
我一直都不管
其实已经编译通过了

There is a generation after the events of error
I have always been regardless of
In fact, has been compiled through the

HOHO,还碰上个同胞啊。
我说的不是在编译时的后编译事件错误(Post-Build Event)。虽然我也碰到过这个错误，但是这个问题可以通过设置正确的环境变量和工作目录来解决。
我碰到的问题是在调试BloodyCake的时候，按F5直接启动会报错，再按F5可以继续。如果直接用Ctrl+F5启动就没问题。所以我觉得是NxOgre的lib或者dll里面缺少了debug信息。不知道你有没有试过运行BloodyCake，有没有碰到过这个问题。而且奇怪的是，刚开始的时候是没有这个错误提示的，只是debug的时候不能跟到NxOgre里面而已，今天早晨突然就出这个错误提示了……SB的VS2005……

To all others: please forgive me to use Chinese, but I am really glad to meet someone also comes from China here.
I think we are talking about two different problems, the one I met is lack of debug information, but his problem is a Post-Build event error.

Well, I've found out the reason: I am using Chinese version of WindowsXP, so there will be an unicode issue when opening the source file. So VS2005 will think "The source file is different from when the module was built.", also the warning 4819 will show up while compiling. This silly problem stops me debugging NxOgre...
To avoid this, we can refer to VS2005 -> Tools -> Options -> Debugging -> General, and uncheck "Require source files to ecactly match the original version".
A small tip: you can check "Hightlight entire source line for breakpoints and current statment", then you can see some changed codes while debugging.