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

tests/gdb/nacl.scons

Index: tests/gdb/nacl.scons
===================================================================
--- tests/gdb/nacl.scons	(revision 9590)
+++ tests/gdb/nacl.scons	(working copy)
@@ -68,6 +68,15 @@
 env.AddNodeToTestSuite(node, ['large_tests'],
                        'run_gdb_step_from_func_start_test')
 
+node = env.CommandTest(
+    'gdb_call.out',
+    command=['${PYTHON}', env.File('call.py')],

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

Nit: "call" is a bit generic.  Can you call this something like "call_from_gdb"
or "manufactured_call"?  Something to indicate that GDB is doing something a
little scary when it hijacks a thread and modifies its registers to run a
function of its choosing. :-)

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

Done.

+    osenv=env_vars + ['GDB_TEST_GUEST=%s' % gdb_test_guest.abspath],
+    extra_deps=[sel_ldr, irt, gdb_test_guest])
+
+env.AddNodeToTestSuite(node, ['large_tests'],
+                       'run_gdb_call_test')
+
 # GDB treats multithreaded programs specially. Provide distinct nexe for
 # multithreaded tests to isolate multiple threads-specific issues.
 gdb_test_guest_thread = env.ComponentProgram(