Archived

This topic is now archived and is closed to further replies.

OK I'm being thick

This topic is 5571 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

My first C compiler was Dev-C++. I''m now using MSVC. When I used to debug with Dev it was easy to step through code. I had no problems using the debugger. But I don''t understand why on MSVC it reaches for example a printf() statement and then opens a box looking for printf.c Why? Why doesn''t it know what this function is? How do I get around it?

Share this post


Link to post
Share on other sites
You are probabl trying to step INTO printf, a library function. The source for the library is on the CD somewhere, but that''s not going to help much, printf ''aint bugged.

I reckon your old debugger and MSVC have swapped the keys for "step over" and "step into".

"Most people think, great God will come from the sky, take away everything, and make everybody feel high" - Bob Marley

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
When you are stepping through your code, step over, rather than step in. F10 is the default key.

Share this post


Link to post
Share on other sites
quote:
Original post by Anonymous Poster
When you are stepping through your code, step over, rather than step in.



Unless, of course, you''re wanting to step into your functions.

Share this post


Link to post
Share on other sites