This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Include access size in find command error message


On 09/26/2012 05:16 PM, Andrew Burgess wrote:
+# Now try a find starting from each global.
+gdb_test "find global_var_1, (global_var_2 + 16), 0xff" \
+    "warning: Unable to access $decimal bytes of target memory at $hex, halting search.\r\nPattern not found."
+
+gdb_test "find global_var_2, (global_var_2 + 16), 0xff" \
+    "warning: Unable to access $decimal bytes of target memory at $hex, halting search.\r\nPattern not found."
+
+gdb_test "find global_var_0, (global_var_2 + 16), 0xff" \
+    "warning: Unable to access $decimal bytes of target memory at $hex, halting search.\r\nPattern not found."

These tests are OK on native target, but fail on gdbserver,


FAIL: gdb.base/find-unmapped.exp: find global_var_1, (global_var_2 + 16), 0xff
FAIL: gdb.base/find-unmapped.exp: find global_var_2, (global_var_2 + 16), 0xff
FAIL: gdb.base/find-unmapped.exp: find global_var_0, (global_var_2 + 16), 0xff


looks you have to tweak your test for remote target.

--
Yao


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]