Re: [edk2-buildtools] Problem source level debugging C tools using VS2003

[Gao, L. <lim...@in...>]

Andrew:
  Compiler adds debug information to the exist .pdb file if these debug information is missed in .pdb file. It does not rewrite the previous .pdb file. So, I am strange why you can't do source level debug. Could you tell me what function in CommonLib can't be debugged correctly? 

Thanks
Liming
-----Original Message-----
From: Andrew Fish [mailto:af...@ap...] 
Sent: 2010年3月23日 4:23
To: edk...@li...
Subject: [edk2-buildtools] Problem source level debugging C tools using VS2003

I had an issue source level debugging a C tool. I figured out the issue was the code was in Sources/C/Common directory and since no -Fd was passed to the compiler the .pdb file had the default name. This meant that each object in the common directory was overwriting the previous objects .pdb file.

If you add -Fd$(@R).pdb to the .c.obj target this problem goes away. Not since the tools had a final link stage in a unique directory the default .pdb name worked for those tools. The problem is the .pdb files for things in common was getting trashed and you could not source level debug through that code. 

I guess you could also add this to the .cpp.obj: rule.  Could some one review my proposed change and check in the fix? 

Andrew Fish






------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
edk2-buildtools-devel mailing list
edk...@li...
https://lists.sourceforge.net/lists/listinfo/edk2-buildtools-devel