Arghhhhh!...I Did It Again
-
I was trying to figure out why this new crash started happening in code that had been working for years. I was running my application in the debugger and had recently made some changes in related library code, so I concentrated on tearing that apart. I finally decided to do a Rebuild All on the entire library solution (39 C++ projects) followed by a Rebuild of the application. Voilà! No more crashing. I occasionally run into this kind of unexplained behavior and I always seem to fiddle around "too long" before I go with the Rebuild All attempt. This time it probably took me less than an hour before I smartened up, but it still annoys me to waste that time. At least I can now go to bed without this bug invading my dreams. :-\ Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
My first guess would be an uninitialized variable floating high or low. In the n years you've been working on it, it floated in the right direction. One day, it decided to float in the wrong direction and then crashitis. Have you now got a faster or slower machine? That causes crashes sometimes. Also beware of #pragma library statements: they do this weird thing of copying libraries all over the place (you'll notice that in C#). On one project, I had 115 copies of the same library and they don't always update. Welcome to the world of versionitis.
-
My first guess would be an uninitialized variable floating high or low. In the n years you've been working on it, it floated in the right direction. One day, it decided to float in the wrong direction and then crashitis. Have you now got a faster or slower machine? That causes crashes sometimes. Also beware of #pragma library statements: they do this weird thing of copying libraries all over the place (you'll notice that in C#). On one project, I had 115 copies of the same library and they don't always update. Welcome to the world of versionitis.
No, it's nothing like that. As I mentioned, a Rebuild All fixed the problem. All the .lib files are stored in the same folder and there are no copies floating around, but thanks for the heads up about that in C#:thumbsup: I have been looking at the library that had the crashing code. It does not have dependency set to the library I had modified, but I have not yet found anything that warrants that. I think I will go ahead and add the dependency, just to help minimize these problems in the future. Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty