[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::visual

Title:	Microsoft Visual C++ bug reports and kits
Notice:	Register in Topic 2. 5.Last for latest Kit
Moderator:	DECWET::THOMASN

Created:	Tue May 17 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	521
Total number of notes:	2938

469.0. "Why does Alpha hit these limitations before Intel?????" by HYDRA::AMORELLI () Mon Feb 24 1997 14:13

Hi,

Oue of our partners is using VC++ 4.2b, WNT 4.0, they've hit the debugger types
limit in a .PDB file.


warning C4168: compiler limit : out of debugger types, delete program database
               'g:\\rat\ui\alpha\windebug\vc42.pdb' and rebuild.


A few things...

o Why does the Alpha compiler hit this limit before Intel?

o Why is it deleting the '.PDB' and rebuilding everything fixes the problem?

o If recompiling the entire project fixes the problem, then we really haven't
  hit the limit. yes/no?

Recompiling the entire project would not be so bad if the compile/link times
were better. I see there are several work-arounds for this problem. Selectively
building modules without debug info. This is not possible without major pains
for the project development team. Re-structuring projects and/or Makefiles
whenever the limit is hit. Not something they want to do when Alpha chokes
and Intel doesn't.

Any info please.

Thanks,

Carl

T.R	Title	User	Personal Name	Date	Lines
469.1	The compiler options	HYDRA::AMORELLI		`Mon Feb 24 1997 14:29`	14
	Here are the options for Alpha compile. m\sldworks\ui\command\mode\gettermode.cpp(673) : warning C4168: compiler limit : out of debugger types, delete program databas 'g:\am\sldworks\ui\alpha\windebug\vc42.pdb' and rebuild cl.exe /nologo /MDd /Gt0 /W3 /GX /Zi /Od /Ob2 /I "../.." /I "../../../thirdpty" /D "_UNICODE" /D "_DEBUG" /D "_AFX_ENABL INLINES" /D "_WINDOWS" /D "WIN32" /D "_AFXEXT" /D "UI_DLL" /D "NT" /D "ALPHA_AXP" /D "_ALPHA_" /D "DRAW_DLL" /D "_AFXDLL" /D " P_DLL" /Fr".\WinDebug/" /Fp".\WinDebug/UIDLL.pch" /Yu"stdam.h" /Fo".\WinDebug/" /Fd".\WinDebug/" /c \am\sldworks\ui\command\mo \gmdynhlt.cpp
469.2		TURRIS::lspace.zko.dec.com::winalski	PLIT Happens...	`Tue Feb 25 1997 10:45`	23
	o Why does the Alpha compiler hit this limit before Intel? A very good question. The debug type info in the PDB file ought to be nearly identical for both platforms. o Why is it deleting the '.PDB' and rebuilding everything fixes the problem? If you modify any routine formal parameter lists or other such stuff that results in the generation of type information, the old types are not removed from the PDB file when you recompile because they might be shared by other files in the application. When you delete the PDB and rebuild, the "dead" types go away. o If recompiling the entire project fixes the problem, then we really haven't hit the limit. yes/no? You hit the limit because of the "dead" types described above. Help is on the way--VC++ 5.0 increases the type index size from 2 to 4 bytes, meaning that the maximum type index is 2 billion, not 64K. --PSW
469.3	Now that makes sense - Thanks...	HYDRA::AMORELLI		`Tue Feb 25 1997 12:18`	11
	I figured the "dead" types were causing the problem. >Help is on the way--VC++ 5.0 increases the type index size from 2 to 4 bytes, >meaning that the maximum type index is 2 billion, not 64K. In a word. Great! Now when explained to the customer in this fashion they'll except the suggestion to upgrade to 5.0. Thanks
469.4	grammar police here	DECC::OUELLETTE		`Tue Feb 25 1997 14:04`	1
	One would hope they accept an upgrade to version 5.0, not except one.
469.5		TURRIS::lspace.zko.dec.com::winalski	PLIT Happens...	`Thu Feb 27 1997 18:42`	6
	RE: .4 Spelling police, actually. Grammatically, the original sentence was correct. --PSW