Folks, I'm investigating the problem - it looks like a bug related to running on Windows Server 2003 only.
I'll post again when I know more. Barry -----Original Message----- From: Discussion of the Rotor Shared Source CLI implementation [mailto:[EMAIL PROTECTED] On Behalf Of Paul Pham Sent: Wednesday, July 02, 2003 12:14 AM To: [EMAIL PROTECTED] Subject: [DOTNET-ROTOR] FW: Debug output problem: ILDB vs. PDB? Hi all, I am trying to build a (fast)checked version of Rotor on Windows Server 2003. Everything builds okay, but when I try to generate output using the SSCLI csc.exe with the /debug switch, I only get an ildb file instead of a pdb file. Whenever I try to debug programs in the SSCLI cordbg, it runs straight through without breaking on the first source line. Similarly, when running these programs with clix unhandled exceptions are not printed. When I use the normal .NET Framework csc.exe with /debug, pdb files are generated, I can step through source code in cordbg, unhandled exceptions are printed, and everything is happy. PDB files are being generated for all the Rotor executables and binaries in sscli\build\v1.x86chk.rotor\Symbols\{Dlls|Exes}, but even when I try to run cordbg on clix, it can't find any debugging symbols. Anyone know what might be the problem? Thanks, Paul
