Re: Bootstrap OpenDylan Win32

Peter Robisch schrieb:
CVPACK: fatal error CK1022: cannot open programm database
<a-mps-directory-never-used-in-the-build-sources>\code\w3i3mv\hi\vc60.pdb
[...]
If that's the issue, stripping mpsplan.lib and mmdw.lib will help.
I think my point is a different point to yours.

No, that is exactly the same problem. pdb files are debugging
information, and the library refers to external debugging files not
present on your machine. Stripping (or building MPS yourself) helps.

With regard to how build-release.bat is supposed to work, I think Peter
Housel or Matthias Hölzl are the people who can help you there. I
haven't used that yet.

Andreas
.

Relevant Pages

  • Re: Building a Release of my Solution
    ... That doesn't equate to the full debugging which is enabled in web.config, ... which generates *.pdb files for true debugging, i.e., setting breakpoints, etc. ... To enable full debugging you need to have the debug symbols generated. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Unable to debug in vs 2008
    ... I am facing issue while debugging on vs 2008. ... i have windows service ... Are you trying to debug an assembly that was built in 2010? ... I'm not sure that 2008 would necessarily be compatible with the .pdb files generated by 2010. ...
    (microsoft.public.dotnet.framework)
  • Re: AccessViolationException originating from mscorjit
    ... it seems to hint at the bug in JIT optimizer. ... debugging from VS, JIT optimizations are suppressed regardless of build ... (we have pdb files even in release mode) ... If your assembly is deployed to GAC, you might have to copy the .pdb over to ...
    (microsoft.public.dotnet.framework)
  • Re: Slightly O/T Problems debugging ....
    ... SteveB wrote: ... ignoring new code when debugging. ... Make sure the .pdb files aren't read-only, ...
    (microsoft.public.vc.language)