User forums > Help

debug issues

<< < (2/2)

cbuser2:

--- Quote from: oBFusCATed on November 15, 2012, 09:17:53 am ---
Have you done a full rebuild?

What command are you using - "Step into" or "Next line" to get this kind of log?

--- End quote ---

I did a rebuild, and using "step into". This is not really a big problem for me, because I can just press "step out" when it steps into a printf(), although I would prefer not having to do this at all. :D

As a point of comparison, I was playing around with MSVC++, and "step into" steps into every c library function, not only printf(). It has a "step over" function, but it is still a pain in the a$$ having to toggle between step into and step over so often.

oBFusCATed:
Hm, so are you complaining that C::B and GDB have done what you've asked them to do?

If you want to go to the next line/statement use the "next line" command and if you want to step into the function on the current line use the step into.
VStudios debugger allows the user to specify function that are skipped by the step-into command, but GDB doesn't support it yet, so you can't have it in C::B, too.

cbuser2:
If posting about a problem is what you would define as complaining, then yes, I suppose I am complaining.

I thought that it was a problem, since it did not happen before, and does not happen with CB for linux(using "step into"). And not sure why only with printf() either.

If stepping into printf() is what CB and gdb are designed to do(which it did not do before, and which does not happen with the linux version), then I suppose this is not a problem at all, so I'll stop wasting everyone's time.

oBFusCATed:
It does step into because for some reason there is debug information for printf and before that there wasn't (probably you've upgraded something).
You can try the same on linux by installing the debug information for glibc :)

Keep in mind that for best experience you should do:

--- Code: ---next
next
next
ooo, this is my function I want to inspect -> step into
next
next
next

--- End code ---
instead of

--- Code: ---step info
step into
uf step into entered this strange functions, so I must step out before I can continue
ooo, this is my function I want to inspect -> step into
step info
step info
step info

--- End code ---

Do you see the difference?

cbuser2:
Yes I do. Thank you.

I am new to debugging, and "step into" was the only thing I knew how to do. :D

Navigation

[0] Message Index

[*] Previous page