 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / Programming / CodeWarrior / December 2003CW9.1 : Caching directories is way too long !
I'm using CW 9.1 on a G4 2*1Gz on a project with more than 300 files and it takes FIFTY seconds to cache the directories of the whole project as shown by the message at the bottom of the project window. this is done each time I begin a debug or run session, and each time I terminate it, and is partially done at a lot of other moments (like destroying a breakpoint). That behaviour was on CW9.0 already. What's stange is that the same directories seems to be scanned more than once. Is it because all my targets are parsed at this time ? 100 seconds : or course this is done SYNCHRONOUSLY, so it's more than the time needed to dive into another job and come back, drink coffee, too much beer, swallow trankillizers, but indeed for coding productivity it seems a bit desesperating (but who speaks about coding any more with such tools ?) So what ? I've tried to reconfigure some preferences randomly (like browser data generation or cache symbolics), of course I've removed object code a lot of times, but my attempts to take control over that nasty behaviour were unsuccessful. Any suggestions ? I suppose I've got some configuration problem... Hello, configuration gods, I need you ! Thanks. > I'm using CW 9.1 on a G4 2*1Gz on a project with more than 300 files > and it takes FIFTY seconds to cache the directories of the whole > project as shown by the message at the bottom of the project window. > this is done each time I begin a debug or run session, and each time I > terminate it, and is partially done at a lot of other moments (like > destroying a breakpoint). That behaviour was on CW9.0 already. I know of no cure other than to learn to hit command-period whenever CW IDE goes catatonic. meeroh  SignatureIf this message helped you, consider buying an item from my wish list: <http://web.meeroh.org/wishlist> > I'm using CW 9.1 on a G4 2*1Gz on a project with more than 300 files > and it takes FIFTY seconds to cache the directories of the whole [quoted text clipped - 19 lines] > Any suggestions ? I suppose I've got some configuration problem... > Hello, configuration gods, I need you ! Thanks. I've seen this before myself. One way to get around this is to turn off Break On C++ Exception. I think that the debugger tries to search for some source file that's hidden with the runtime sources. If you want to keep Break On C++ Exception turned on, then you might want to try adding an access path that points into the shielded runtime folder. I have not tried this myself, but I suspect it will stop all that caching. SignatureIsaac Wankerl Metrowerks Mac Software Developer > > I'm using CW 9.1 on a G4 2*1Gz on a project with more than 300 files > > and it takes FIFTY seconds to cache the directories of the whole [quoted text clipped - 12 lines] > an access path that points into the shielded runtime folder. I have not > tried this myself, but I suspect it will stop all that caching. I have frequently and intermittently seen this as well, at the same places, starting/stopping debugging and clearing (not setting) a breakpoint. The status line at the bottom of the project windows flashes a bunch of 'Caching directory' messages. In between which are some 'Searching' messages, usually you can't read this (they go by too fast) but when it stops it is usually on one of those messages and it is always for the same two files: ExceptionPPC.cp and NewMore.cp. This happens with all the projects as their symbols are loaded. It is especially noticable for me since I am linking my app with a large dynamic library and loading a plugin. The messages on the plugin's project window flash when the app loads it, not when debugging starts. I am linking against the BSD libraries using MSL_C++_BSD_C_Mach-O_D.lib and BSD_Runtime_Mach-O_D.lib. If I switch to the non-debug versions of these libraries the problem goes away. And like you said if I turn off Break On C++ Exception it goes away (didn't know about that before, thank!). I have tried rebulding those system libraries but it didn't help. OS 10.2.8, CW 9.0. This is highly annoying and can add 2-3 minutes to every debugging cycle. Hope someone can track this down! Robert > > I'm using CW 9.1 on a G4 2*1Gz on a project with more than 300 files > > and it takes FIFTY seconds to cache the directories of the whole [quoted text clipped - 9 lines] > an access path that points into the shielded runtime folder. I have not > tried this myself, but I suspect it will stop all that caching. The trick works, thanks, However, I've set a recursive system access path to "{Compiler}Mac OS X Support/Libraries/Runtime" but this does not help. > I've seen this before myself. One way to get around this is to turn off > Break On C++ Exception. Great! This has been a big nuisance to me also. But please, where can the "Break On C++ Exception" preference be found? >> I've seen this before myself. One way to get around this is to turn off >> Break On C++ Exception. > >Great! This has been a big nuisance to me also. >But please, where can the "Break On C++ Exception" preference be found? It is in the Debug menu when you are debugging. Ron SignatureNew from Metrowerks The CodeWarrior Wireless Development Kit for Symbian OS, SEMC P900 Edition Easy-to-use, integrated tools and hardware for SEMC P900 Development http://www.metrowerks.com/MW/Develop/Wireless/Symbian/SymbianWDKC.htm Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com > Any suggestions ? I suppose I've got some configuration problem... Only for mach-o, right? I noticed this right after I added a mach-o target in addition to the PEF targets I'd been working on for months. >> Any suggestions ? I suppose I've got some configuration problem... > >Only for mach-o, right? I noticed this right after I added a mach-o target >in addition to the PEF targets I'd been working on for months. This should only happen on the intiali launch but I've seen it happen by just changing some headers. Mach-O and searching the system and all the separate includes takes some time. We are working on improving this. Ron SignatureNew from Metrowerks The CodeWarrior Wireless Development Kit for Symbian OS, SEMC P900 Edition Easy-to-use, integrated tools and hardware for SEMC P900 Development http://www.metrowerks.com/MW/Develop/Wireless/Symbian/SymbianWDKC.htm Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com > This should only happen on the intiali launch but I've seen it happen by > just changing some headers. Mach-O and searching the system and all the > separate includes takes some time. We are working on improving this. And you may already have, somewhat. Since upgrading to 9.1 I notice performance that I would characterize as quite sluggish, 10-15 seconds of directory scanning, whereas with 9.0 it was literally making me crazy. Under 9.0 it started out slow, but seemed to gradually get slower with subsequent launches, until it would take well over a minute--almost as if it were scanning the same directories multiple times. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.