tests/gdb/call.py - Issue 10896004: Don't modify memory access right when changing data in debug stub.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: tests/gdb/call.py

Issue 10896004: Don't modify memory access right when changing data in debug stub. (Closed) Base URL: svn://svn.chromium.org/native_client/trunk/src/native_client/

Patch Set: Created 8 years, 3 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

OLD	NEW
(Empty)
	1 # -- python --

	2 # Copyright (c) 2012 The Native Client Authors. All rights reserved.

	3 # Use of this source code is governed by a BSD-style license that can be

	4 # found in the LICENSE file.

	5

	6 import gdb_test

	7 import os

	8

	9

	10 def test(gdb):

	11 gdb.Command('break test_call')
	Mark Seaborn 2012/08/30 16:55:57 Why not just set a breakpoint on main()? Then you 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. Show quoted text On 2012/08/30 16:55:57, Mark Seaborn wrote: > 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()? Done.
	12 assert gdb.ResumeCommand('continue')['reason'] == 'breakpoint-hit'

	13 gdb.Command('delete 1')

	14 assert gdb.ResumeCommand('finish')['reason'] == 'function-finished'

	15 assert gdb.Eval('test_call(1)') == '2'

	16

	17

	18 if __name__ == '__main__':

	19 gdb_test.RunTest(test, 'call', os.environ['GDB_TEST_GUEST'])

OLD	NEW

« src/trusted/debug_stub/win/platform_impl.cc ('K') | « src/trusted/debug_stub/win/platform_impl.cc ('k') | tests/gdb/gdb_test_guest.c » ('j') | tests/gdb/gdb_test_guest.c » ('J')