Home
last modified time | relevance | path

Searched refs:gdb (Results 1 – 25 of 156) sorted by relevance

1234567

/external/valgrind/gdbserver_tests/
DMakefile.am25 hginfo.stdinB.gdb \
30 hgtls.stdinB.gdb \
34 mcblocklistsearch.stdinB.gdb \
39 mcbreak.stdinB.gdb \
45 mcclean_after_fork.stdinB.gdb \
54 mcinfcallRU.stdinB.gdb \
58 mcinfcallWSRU.stdinB.gdb \
70 mcleak.stdinB.gdb \
76 mcmain_pic.stdinB.gdb \
82 mcmain_pic.stdinB.gdb \
[all …]
DREADME_DEVELOPERS7 By default, these tests are running with the gdb found at
10 If you want to test with another gdb version, you can do:
11 make regtest GDB=/path/to/another/gdb
13 or (to just run the gdbserver tests with another gdb):
17 gdbserver_tests/make_local_links /path/to/another/gdb
20 The minimum version to run the tests is gdb >= 6.5.
26 The tests have been run on various platforms using gdb versions >= 7.2
27 and on some platforms gdb 7.0 and 7.1.
28 Some gdb tests implies a gdb >= 7.2. (these are automatically disabled
30 Test behaviour with gdb < 7.0 is unknown: some might fail,
[all …]
DmcinfcallWSRU.stdinB.gdb1 # connect gdb to Valgrind gdbserver:
21 print whoami("thread 1 inferior call pushed from gdb in mcinfcallWSRU.stdinB.gdb")
23 print whoami("thread 2 inferior call pushed from gdb in mcinfcallWSRU.stdinB.gdb")
25 print whoami("thread 3 inferior call pushed from gdb in mcinfcallWSRU.stdinB.gdb")
27 print whoami("thread 4 inferior call pushed from gdb in mcinfcallWSRU.stdinB.gdb")
Dmake_local_links63 ln -f -s "$GDB" gdbserver_tests/gdb
66 GDBVERSIONLINE=`gdbserver_tests/gdb --version | head -n 1`
74 check_version 7.0 gdbserver_tests/gdb "gdbserver gdb tests"
78 check_version 7.1 gdbserver_tests/gdb.pic "pic executable tests"
85 check_version 7.1 gdbserver_tests/gdb.step "gdbserver next/step/... tests ARM"
87 check_version 7.0 gdbserver_tests/gdb.step "gdbserver next/step/... tests"
91 check_version 7.2 gdbserver_tests/gdb.eval "gdbserver eval tests"
Dmcmain_pic.vgtest1 # test that gdbserver/gdb properly handle a PIC executable
4 # The content of the auxv data can be shown by gdb using
5 # gdb command 'info auxv'
6 prereq: test -e gdb.pic
11 progB: gdb
13 stdinB: mcmain_pic.stdinB.gdb
Dmcwatchpoints.vgtest3 # We need a non buggy gdb.step as watchpoints are placed after a "step".
4 prereq: test -e gdb -a -f gdb.step
9 progB: gdb
11 stdinB: mcwatchpoints.stdinB.gdb
DmcinfcallWSRU.vgtest8 # We need a non buggy gdb.step on arm thumb.
10 prereq: test -e gdb -a -f gdb.step && ! ../tests/os_test darwin
13 progB: gdb
15 stdinB: mcinfcallWSRU.stdinB.gdb
Dmcvabits.vgtest2 prereq: test -e gdb
7 prereq: test -e gdb.eval
8 progB: gdb
10 stdinB: mcvabits.stdinB.gdb
DmcinfcallWSRU.stderrB.exp1 relaying data between gdb and process ....
28 gdb commands changing registers (pc, sp, ...) (e.g. 'jump',
29 set pc, calling from gdb a function in the debugged process, ...)
37 gdb commands changing registers (pc, sp, ...) (e.g. 'jump',
38 set pc, calling from gdb a function in the debugged process, ...)
46 gdb commands changing registers (pc, sp, ...) (e.g. 'jump',
47 set pc, calling from gdb a function in the debugged process, ...)
Dnlgone_return.vgtest1 # test that a normal (successful) return is properly passed on to gdb.
7 prereq: test -e gdb && ! ../tests/arch_test tilegx
8 progB: gdb
10 stdinB: nlgone_return.stdinB.gdb
Dmcbreak.vgtest3 prereq: test -e gdb -a -f gdb.step
8 progB: gdb
10 stdinB: mcbreak.stdinB.gdb
Dnlgone_abrt.vgtest1 # test that a fatal SIGABRT signal is properly passed on to gdb.
7 prereq: test -e gdb
8 progB: gdb
10 stdinB: nlgone_abrt.stdinB.gdb
Dnlgone_exit.vgtest1 # test that an exit (with return value) is properly passed on to gdb.
8 prereq: test -e gdb
9 progB: gdb
12 stdinB: nlgone_exit.stdinB.gdb
Dnlpasssigalrm.vgtest5 # it directly to the process, without roundtrip to gdb.
10 prereq: test -e gdb
11 progB: gdb
13 stdinB: nlpasssigalrm.stdinB.gdb
Dmcsignopass.vgtest3 # the gdb output will not contain the signal handling
7 prereq: test -e gdb
12 progB: gdb
14 stdinB: mcsignopass.stdinB.gdb
Dnlsigvgdb.vgtest1 # Tests the case when gdb sends a character to gdbserver while
10 prereq: test -e gdb -a -f vgdb.invoker
11 progB: gdb
13 stdinB: nlsigvgdb.stdinB.gdb
/external/lldb/utils/test/
Ddisasm.py35 gdb = pexpect.spawn(('gdb %s' % gdb_options) if gdb_options else 'gdb')
37 gdb.logfile_read = sys.stdout
38 gdb.expect(gdb_prompt)
42 gdb.sendline(cmd)
43 gdb.expect(gdb_prompt)
46 gdb.sendline('file %s' % exe)
47 gdb.expect(gdb_prompt)
50 gdb.sendline('disassemble %s' % func)
51 gdb.expect(gdb_prompt)
54 gdb_output = gdb.before
[all …]
DREADME-disasm3 command line. We invoke gdb on an executable, try to disassemble a function,
13 gdb commands: ['set shlib-path-substitutions /usr /Developer/Platforms/iPhoneOS.platform/Developer/…
14 gdb options: -arch armv7
19 GNU gdb 6.3.50-20050815 (Apple version gdb-1518) (Sat Feb 12 02:56:02 UTC 2011)
30 (gdb) disassemble printf
70 (gdb) x /2b 0x0704cdd0
72 (gdb) x /2b 0x0704cdd2
74 (gdb) x /2b 0x0704cdd4
76 (gdb) x /2b 0x0704cdd6
78 (gdb) x /2b 0x0704cdd8
[all …]
/external/v8/tools/
Dgdb-v8-support.py60 t_u32 = gdb.lookup_type('unsigned int')
61 t_u64 = gdb.lookup_type('unsigned long long')
131 gdb.pretty_printers.append(v8_pretty_printers)
144 v = gdb.parse_and_eval(vstring)
148 class V8PrintObject (gdb.Command):
151 super (V8PrintObject, self).__init__ ("v8print", gdb.COMMAND_DATA)
154 gdb.execute('call __gdb_print_v8_object(%d)' % v)
158 class FindAnywhere (gdb.Command):
163 super (FindAnywhere, self).__init__ ("find-anywhere", gdb.COMMAND_DATA)
166 result = gdb.execute(
[all …]
/external/llvm/docs/
DDebuggingJITedCode.rst89 $ gdb --quiet --args $BINPATH/lli -use-mcjit showdebug.ll 5
91 (gdb) b showdebug.c:6
95 (gdb) r
101 (gdb) p n
103 (gdb) p f
105 (gdb) n
107 (gdb) p f
109 (gdb) b showdebug.c:9
111 (gdb) c
116 (gdb) p f
[all …]
/external/autotest/client/site_tests/security_ptraceRestrictions/src/
Dptrace-restrictions.sh39 OUT=$(gdb -ex run -ex quit --batch ./sleeper </dev/null 2>&1)
50 OUT=$(gdb -ex "attach $pid" -ex "quit" --batch </dev/null 2>&1)
67 OUT=$(gdb -ex "attach 1" -ex "quit" --batch </dev/null 2>&1)
89 OUT=$(gdb -ex "attach $pid" -ex "quit" --batch </dev/null 2>&1)
101 OUT=$(gdb -ex "attach $pid" -ex "quit" --batch </dev/null 2>&1)
113 OUT=$(gdb -ex "attach $pid" -ex "quit" --batch </dev/null 2>&1)
125 OUT=$(gdb -ex "attach $pid" -ex "quit" --batch </dev/null 2>&1)
/external/valgrind/coregrind/m_gdbserver/
DREADME_DEVELOPERS11 gdb debugger typically is used to debug a process running
12 on the same machine : gdb uses system calls (such as ptrace)
18 gdb can also debug processes running in a different computer
22 gdb does this by sending some commands (e.g. using tcp/ip) to a piece
24 gdb stub in small boards, or gdbserver when the remote computer runs
25 an OS such as GNU/linux) will provide a set of commands allowing gdb
29 associated replies is the gdb remote serial protocol, which is
30 documented in Appendix D of gdb user manual.
32 The standard gdb distribution has a standalone gdbserver (a small
34 to allow gdb to remotely debug process running on a linux or MacOS or
[all …]
/external/valgrind/solaris/
Dgdb-sol-thread.patch1 --- gdb-7.6.2/gdb/sol-thread.c.orig 2013-12-26 22:02:08.930437615 +0000
2 +++ gdb-7.6.2/gdb/sol-thread.c 2013-12-26 22:05:06.506977611 +0000
/external/lldb/examples/test/tmp/
Dlldb_log-x86_64-clang-TestBreakpointCommand.BreakpointCommandTestCase.test_with_dwarf.txt11 <lldb.process.gdb-remote.async> ProcessGDBRemote::AsyncThread (arg = 0x7fabc0997600, pid = 0) threa…
12 <lldb.process.gdb-remote.async> ProcessGDBRemote::AsyncThread (arg = 0x7fabc0997600, pid = 0) liste…
37 <lldb.process.gdb-remote.async> ProcessGDBRemote::AsyncThread (arg = 0x7fabc1882000, pid = 55289) G…
38 <lldb.process.gdb-remote.async> ProcessGDBRemote::AsyncThread (arg = 0x7fabc1882000, pid = 55289) g…
39 <lldb.process.gdb-remote.async> ProcessGDBRemote::AsyncThread (arg = 0x7fabc1882000, pid = 55289) t…
52 <lldb.process.gdb-remote.async> ProcessGDBRemote::AsyncThread (arg = 0x7fabc0bed200, pid = 55292) G…
53 <lldb.process.gdb-remote.async> ProcessGDBRemote::AsyncThread (arg = 0x7fabc0bed200, pid = 55292) g…
54 <lldb.process.gdb-remote.async> ProcessGDBRemote::AsyncThread (arg = 0x7fabc0bed200, pid = 55292) t…
/external/valgrind/docs/internals/
Darm_thumb_notes_gdbserver.txt21 by gdb. As gdb is giving breakpoints without the thumb bit set,
33 as this value will be given back to gdb. gdb uses the thumb bit a.o.
35 Such a guess is needed for gdb commands such as next/step/...
62 * gdb 7.0 is buggy with thumb code
63 The logic of gdb to guess the next PC in thumb code is not working
64 properly in version gdb 7.0. Several gdbserver tests are disabled
65 on ARM if gdb version is < 7.1.
70 gdb address and gdbserver failed).
73 This made breakpoints work, but then gdb next/step/... was then failing

1234567