Bugzilla – Full Text Bug Listing
| Summary: | Show function arguments in the Debug view | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Samuel Hultgren <taortan> |
| Component: | cdt-debug | Assignee: | cdt-debug-inbox <cdt-debug-inbox> |
| Status: | NEW --- | QA Contact: | Jonah Graham <jonah> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | dalexiev, elaskavaia.cdt, pawel.1.piech |
| Version: | 7.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
What is wrong with Variables view? Sorry for the late reply. (In reply to comment #1) > What is wrong with Variables view? The Variables view only shows values and variables for the current function. It doesn't cover the case when you are several calls deep, for example, main calls func1 with some argument, which calls func2 with some other arg. When debugging func2 it would be nice to be able to see what arguments all previous functions where called with, in this case, func1 and main. It shows variables for the function you selected. Select function in the next stack frame and you will see another set of variables. |
Build Identifier: 20100218-1602 It would be nice if the Debug view could show the arguments on the Stack. for example, as it is now when debugging the function func with signature : int func(int intarg, char* strarg, struct myStruct obj); the Debug view shows func() at C:/tmp/tests/args/Debug/../src/args.c:20 The proposition is that it would be nice to show something like more like what the gdb 'where' command shows: #0 func (intarg=2, strarg=0x402029 "two", structptr=...) at ../src/args.c:20 If this information could be used more in the Stack of the Debug view. Reproducible: Always