[Bug gdb/22293] New: find command's "halting search" warning missing against gdbserver

["palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=22293

            Bug ID: 22293
           Summary: find command's "halting search" warning missing
                    against gdbserver
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: palves at redhat dot com
  Target Milestone: ---

Currently, native-testing gdb.base/find-unmapped.exp we see:

 find global_var_0, global_var_2, 0xff
 warning: Unable to access 398 bytes of target memory at 0x7ffff7ff5e83,
halting search.
 Pattern not found.
 (gdb) PASS: gdb.base/find-unmapped.exp: find global_var_0, global_var_2, 0xff

While with native-extended-gdbserver we get:

 find global_var_0, global_var_2, 0xff
 Pattern not found.
 (gdb) FAIL: gdb.base/find-unmapped.exp: find global_var_0, global_var_2, 0xff

The test fails because the testcase is expecting the "halting search" warning.
And the warning is missing because gdbserver supports the search memory packet,
and in that case, the warning is output by gdbserver instead of gdb.

Printing the warning in gdbserver's terminal doesn't really help users.  It'd
be much better if the search memory packet was extended to allow reporting back
the memory range that couldn't be read, and then have GDB print the warning,
instead of gdbserver.

-- 
You are receiving this mail because:
You are on the CC list for the bug.