[v2,1/2] gdb/testsuite: allowed for function_range to deal with mangled functions
Commit Message
When calling get_func_info inside a test case, it would cause failures
if the function was printed using a C++ style mangled name. The current
patch fixes this by allowing for mangled names along with the current
rules.
---
gdb/testsuite/lib/dwarf.exp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
>>>>> "Bruno" == Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org> writes:
Bruno> When calling get_func_info inside a test case, it would cause failures
Bruno> if the function was printed using a C++ style mangled name. The current
Bruno> patch fixes this by allowing for mangled names along with the current
Bruno> rules.
Looks good. Thank you.
Tom
On 09/11/2022 18:15, Tom Tromey wrote:
>>>>>> "Bruno" == Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org> writes:
> Bruno> When calling get_func_info inside a test case, it would cause failures
> Bruno> if the function was printed using a C++ style mangled name. The current
> Bruno> patch fixes this by allowing for mangled names along with the current
> Bruno> rules.
>
> Looks good. Thank you.
Thanks for the review. Which email should I add to the Approved-by tag?
Bruno> Thanks for the review. Which email should I add to the Approved-by tag?
It's not super important to me but I guess as a rule of thumb it seems
safe to use whatever address the approval is sent from.
Tom
On 10/11/2022 14:44, Tom Tromey wrote:
> Bruno> Thanks for the review. Which email should I add to the Approved-by tag?
>
> It's not super important to me but I guess as a rule of thumb it seems
> safe to use whatever address the approval is sent from.
Thanks, I pushed the whole series!
@@ -400,7 +400,7 @@ proc function_range { func src {options {debug}} } {
if { $func_length != 0 } {
set func_pattern "$func_pattern\\+$func_length"
}
- set test "x/2i $func+$func_length"
+ set test "with print asm-demangle on -- x/2i $func+$func_length"
gdb_test_multiple $test $test {
-re ".*($hex) <$func_pattern>:\[^\r\n\]+\r\n\[ \]+($hex).*\.\r\n$gdb_prompt $" {
set start $expect_out(1,string)