User forums > Help

Debugger Step-Into with multiple calls on same line

(1/3) > >>

vid512:
Trying to debug code like following:

--- Code: ---      func1(func2());

--- End code ---

I can't step into func1. Shift-F7 (the 'Step Into' command) only steps into func2, and upon return from it, the debugger goes right to the following line. What I would expect upon return from func2() is to remain at the same line in source, allowing to step into func1() as well.

Is this impossible in C::B, or am I missing something?

Using nightly C::B 7550 from 30th October, on Windows 7 64-bit, project is compiled with MS Visual C++, cdb.exe from 32-bit "Debugging Tools for Windows (x86)" is used as debugger.

ollydbg:
I just use such code under MinGW GCC4.4.5+GDB(cvs)
There is no such problem, I first step into func2, then func1.


--- Code: ---void func1(int b)
{
    int a;
    a = b;
};

int func2()
{
    int a;
    a = 1;
    return a;
};

int main ()
{
    func1(func2());
}
--- End code ---

So, it looks like cdb.exe has some problems.

vid512:
Thanks. I tested on Ubuntu/gcc/gdb now, and there everything works as expected. I'll try with MinGW, to see if this really is limitation of cdb (or of C::B usage of cdb).

vid512:
Yep, definitively seems to be an issue related to cdb.exe. The debugging same project on same system with same C::B works fine with MinGW gdb, but errs as described with MS cdb.

Is there any other debugger C::B can use with MS Visual C++ produced files?

oBFusCATed:
No, unfortunately. Have you tried the debugger branch nightly?
There were some fixes and improvements related to debugging in general and related to cdb, too.
I don't think this kind of bug has been reported or fixed unfortunately.

I'll check it as soon as possible.

Can you past the debugger's debug log (not the normal log but the raw log with the output from cdb.exe).
To enable this log go to 'settings -> compiler & debugger -> debugger -> something about debugger's log'.

Navigation

[0] Message Index

[#] Next page