Hello,
I have a C++/IDE question, let's say I have a class ABC which defines a methodas the name of the function suggests all classes need to define it. Now, how do you guy search for all calls to that mandatoryMethod on this particular class ABC?Code:ABC::mandatoryMethod(...){}
Since this methods is common for all classes we will get plenty of search results.... I wonder if there is a clever way to get only those of our interest (called on class ABC)
Regards,
Martin
Most decent C++ aware IDEs have things like
- find declaration
- find definition
- find references
Highlight the thing you're interested and pick door number 3.
@Salem, I gave visual studio a try and it looks like it finds all occurences of the method no matter if a call or declaration not to mention a care of call on specific class....do you agree?
Also its not possible for IDE to find all references IMHO, because methods may be called by a pointer or in a way of inheritance or in runtime even dynamically in the runtime...
Why do you want to find all calls of that method? Usually I'd imagine it is to perform a rename, and your IDE may have a specific refactoring tool for that, but then indirect invocation of the method through a pointer wouldn't matter.
Why? I get into new project written in C++ and I try to get the code flow. For example I recognize some point in the program which I am sure will be called, lets call itQuote:
Originally Posted by laserlight
now the point is to find all callers of that function so I establish a flow... and this is in essence my question...lets neglect debugger and breakpoints for the moment.Code:classABC::functionABC() {...}
Oh, but that wouldn't help you understand the code flow, if by that you mean the flow of control through the program. That would be done by tracing function call graphs rather than by finding all callers of specific functions.
I think "references" just means the places where the name refers to the particular function (or object, class, etc) rather than something else with the same name. That said, static analysis can handle inheritance and certain function pointer usage.Quote:
Originally Posted by MartinR
Yeah and these function call graphs can't be generated by any IDE right? Only the debugger (by means of a breakpoint) or somebody could generate it base on their experience?Quote:
Originally Posted by laserlight
If you're looking for run-time, you need some kind of profiling tool.
Gprof - Wikipedia
@Salem, the problem is I work with the firmware on the embedded device - no OS no nothing. So I end up using GDB to trace calls...do you see any other way?
Which hardware device?
If you're fortunate enough, maybe your CPU has hardware breakpoint or trace registers.
If so, you could implement a local handler to increment a local counter that doesn't involve stopping GDB every time the function is called.
You can then use GDB to just examine the counter at the end of the test.
Its Audio DSP, yes it does support HW brakpoints. As for the custom handler, yes this is actaully a good idea - such handler could record all callers in some data structure (say a linked list) which can be read later on. In the meantime I managed to hookup HW debugger to this device and now I can easily backtrace the code execution for some particular scenario at least.
Thanks!