Visual C/C++ ver. 6 Trouble :(

[Adak]

I have a C program, and it runs OK, in Visual C 6, until I want to step through the code - then:

Every few lines of code, *UP* pops a "Find Source" window, and it would like to know where it can find the file "printf.c", or "fopen.c" or "fputc.c", or any of numerous other C functions, in the code.

I have tried everything to get it to stop this nonsense, but it continues unabated. Note that the program runs fine, in both release or debug versions.

After closing this window, the *Disassembly Window* pops up, and now I can only step through my code, in assembly - "Assembly!!? Where's the 12 gauge? I'm a gonna bag me one compiler, I do believe."

I've also loaded the program as a C++ program, (with .cpp in the filename extension), but it makes no difference.

I've never seen this "Find Source" pop-up window, before. This is a default install of Vis.C/C++ 6.0, in every respect, running on a WindowsXP system, with all updates.

Thanks.

[Sebastiani]

Strange. You know they just recently (week or two ago) came out with a major security patch - I'm assuming you've gotten that one already then? If nothing else, try a reinstall, obviously.

[hk_mp5kpdw]

Kinda sounds like you're trying to step into the standard functions fopen/fprintf/etc... If that's the case then stop trying, always step over (never into) such functions.

[bithub]

If that's the case then stop trying, always step over (never into) such functions.

I think that's your answer.

[Elysia]

I think that's your answer.

Well, no, that's not the answer.
Just browse on your hard drive where the source files are installed (don't know where that is on such an ancient IDE such as v6, however).
If you don't do that, then VS can obviously not show you the source and does the next best thing - it shows the assembly of the function.
If neither of the above is for you, then just step over them (F10).

And btw, if you can, upgrade.

[bithub]

Why would he want to step through the source code for printf and the other standard functions?

[Elysia]

You can use it to debug why your output is wrong, for example. Subtle things the eye might not spot.
Regardless, I don't like to block options that are available. The programmer will choose what is best, not us.

[Adak]

Thanks, everyone!

I haven't used VC 6 in quite a while, and in a late-nite session, I got tangled up with the project/workspace set up, and somehow the step and step into keys both started acting the same. I had forgotten VC would step into a header function, as well.

Making a new project fixed the problem and thanks for the tip about stepping into and stepping over during debugging. Obviously, I need to step into some of my functions, but I have no need to step into the header's functions.

The program is now fixed and running. In fact, it's enumerated 420 million Sudoku grids, already.

Which is why I was using VC 6 for the compiler. It generates faster programs for Windows, than Turbo C/C++ 1.01.

After reading the post about Open Watcom's compiler, I'll have to give it a try, also.

Speed is very important for this program. It has a LONG way to go before it's done, but that will be another thread entirely.

Thanks again!

[cpjust]

Which is why I was using VC 6 for the compiler. It generates faster programs for Windows, than Turbo C/C++ 1.01.

I believe VC++ 2008 would make a huge speed difference compared to VC++ 6.0. Maybe you should try it, since it's free...

[bithub]

I believe VC++ 2008 would make a huge speed difference compared to VC++ 6.0. Maybe you should try it, since it's free...

Has Microsoft's C compiler really changed all that much since VC6? I know the C++ compiler is way different (and way more standard), but I wasn't aware of any major changes to the C compiler.