Don't modify memory access right when changing data in debug stub.

tests/gdb/call.py

Index: tests/gdb/call.py
===================================================================
--- tests/gdb/call.py	(revision 0)
+++ tests/gdb/call.py	(revision 0)
@@ -0,0 +1,19 @@
+# -*- python -*-
+# Copyright (c) 2012 The Native Client Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+import gdb_test
+import os
+
+
+def test(gdb):
+  gdb.Command('break test_call')

[Mark Seaborn, 2012/08/30 16:55:57]

Why not just set a breakpoint on main()?  Then you don't need to delete the
breakpoint, and you don't need the C code to call test_call()?

[halyavin, 2012/08/31 08:01:24]

Done.

+  assert gdb.ResumeCommand('continue')['reason'] == 'breakpoint-hit'
+  gdb.Command('delete 1')
+  assert gdb.ResumeCommand('finish')['reason'] == 'function-finished'
+  assert gdb.Eval('test_call(1)') == '2'
+
+
+if __name__ == '__main__':
+  gdb_test.RunTest(test, 'call', os.environ['GDB_TEST_GUEST'])