| Summary: | CU expansion problem for parameters | ||
|---|---|---|---|
| Product: | gdb | Reporter: | Jan Kratochvil <jan> |
| Component: | symtab | Assignee: | Jan Kratochvil <jan> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | keiths |
| Priority: | P2 | ||
| Version: | HEAD | ||
| Target Milestone: | --- | ||
| Host: | Target: | x86_64-unknown-linux-gnu | |
| Build: | Last reconfirmed: | ||
The dependency on CU expansion is a physname regression. But the feature of originally-typed-parameters symbols was not present before physname at all. + prephysname b 'f(int) + prephysname -readnow b 'f(int) + physname b 'f(int) + physname -readnow b 'f(int) b 'f(int_typedef) + HEAD b 'f(int) + HEAD -readnow b 'f(int) b 'f(int_typedef) [patch] physname-related CU expansion issue for C++ (PR 12708) http://sourceware.org/ml/gdb-patches/2011-04/msg00551.html [commit+commit 7.3] [patch] physname-related CU expansion issue for C++ (PR 12708) http://sourceware.org/ml/gdb-patches/2011-05/msg00185.html |
typedef int int_typedef; void f (int_typedef x) {} gcc -c -g ./gdb-clean -q -nx ./1.o -ex "complete b 'f(" -ex q b 'f(int) ./gdb-clean -readnow -q -nx ./1.o -ex "complete b 'f(" -ex q b 'f(int) b 'f(int_typedef) -readnow should never affect GDB user visible behavior.