sparge
Joined: 11 Apr 2005
Posts: 371
|
 Posted: Wed Nov 24, 2010 1:36 pm Post subject: Asking for ull debug info makes CLRWIN invisible to SLINK!? |
 |
|
Wow, I'm needing a lot of support today ...
Something else I just got around to using the knowledge base to refresh my memory on (it fails me on this subject evey few months) is how to get PARAMETERs displayed in SDBG. I always forget I need to check "full debug information". So I just did this, and now when I build, SLINK whinges as follows:
WARNING the following symbols are missing:
MODULE CLRWIN
Now the knowledge base has something to say on this subject too. It says that the majority of such problems are caused by an incorrect installation of FTN95, and/or multiple copies of salflibc.dll on the path. So I used the Salford diagnostic tool, and somewhat to my surprise, the only copy of salflibc.dll reported is the installation copy. It seems last time I installed, I didn't plonk a copy in the windows system directory. So I rectified that oversight but it didn't help.
So my question is, why does specifying full debug information provoke SLINK into sudden inability to find MODULE CLRWIN? It is quite happy that it knows where it is if I don't ask for full debug information ... |
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
