Debug assertion dialog references non-existant file

[jbreher]

I am in the process of trying to debug a confusing error. If interested in
the background, see:
http://msdn.microsoft.com/newsgroups/default.aspx?cat=&lang=&cr=&guid=&sloc=en-us&dg=microsoft.public.vc.mfc&tid=4b01b52f-ed20-4e7d-9928-7bc6e8785b80&amid=57a47b89-4f22-48d5-b95a-43bf072466df&answer=-1&p=1&stgxml=http%3a%2f%2fmsdn.microsoft.com%2fnewsgroups%2fsettings.xml&mid=a9d5aa55-d0ca-4062-bf48-d1fde7188e36

At any rate, if I leave the app in a 'failed' state long enough, VS throws
up the following dialog:

Microsoft Visual C++ Debug Library [X]
(X) Debug Assertion Failed!
Program: ...
File: f:\sp\vctools\vc7libs\ship\atlmfc\src\mfc\sockcore.cpp
Line: 183
For information on how your program can cause an assertion failure, see the
Visual C++ documentation on asserts.
(Press Retry to debug the application)
[Abort][Retry][Ignore]

All well and good, save for the fact that <I>there is no f: drive on my
system</I>.
Indeed, none of the drives has a directory sp off the root.

What is this trying to indicate, and how do I address the error?

[Alex Blekhman]

Post by jbreher
drive on my
system</I>.
Indeed, none of the drives has a directory sp off the root.
What is this trying to indicate, and how do I address the error?

The file path in assertion dialog box is the original path where
the file was located when the library had been built. Press
"Retry" button, so debugger will stop at the right spot in the
code. Then you will be able to examine the call stack. While in
debugger open this file manually (find it in MFC's source
directory). Then debugger may pick it up. However, even if
debugger is unable to match executable image to a source file, you
can always open a file and see what is actually there.

HTH
Alex