Just tried installing Carbide.vs 3 today and having trouble getting RDebug output to appear in the Output window.
Setup:
- Using S60_3rd_MR.
- Breakpointing works in VS and Carbide.c++ 1.2.
- Debug output works fine in Carbide.c++ 1.2.
- RDebug output is going to $TEMP/epocwind.out as expected.
But, nothing is turning up in VS output window except DLL load/unload messages like
Any suggestions?Command Line Args:
The thread 'Win32 Thread' (0xdc) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xe40) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xa8c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x139c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x11e0) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x173c) has exited with code 0 (0x0).
...
Another small annoyance: is it possible to get epocwrapper to stop epoc and allow to see the stack trace during a panic or Leave in carbide.vs, like happens in Carbide.c++?



