Searched refs:vgdb (Results 1 – 25 of 92) sorted by relevance
1234
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue3 echo vgdb launched process attached\n4 monitor v.set vgdb-error 9999998 shell ./simulate_control_c --vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue 1 grep main nlvgdbsigqueue.st…10 # send SIGUSR1/SIGUSR1 in a few seconds, after vgdb has attached11 # vgdb will attach when it will receive the control-c12 shell ./send_signal USR1 --vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue 0 grep attachedwaitingforsigusr…13 shell ./send_signal USR1 --vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue 1 grep attachedwaitingforsigusr…15 echo continuing to have vgdb interrupted by simulate_control_c\n18 # Now vgdb should have received the interrupt, and so has[all …]
3 vgopts: --tool=memcheck --vgdb=yes --vgdb-error=0 --vgdb-prefix=./vgdb-prefix-mchelp6 progB: vgdb7 argsB: --wait=60 --vgdb-prefix=./vgdb-prefix-mchelp -c help -c help debug -c v.kill
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-nlsigvgdb3 echo vgdb launched process attached\n4 monitor v.set vgdb-error 99999910 shell ./simulate_control_c --vgdb-prefix=./vgdb-prefix-nlsigvgdb 1 grep continuing nlsigvgdb.stderr…
1 # test that vgdb can invoke a process when all threads are in WaitSys mode.5 vgopts: --tool=memcheck --vgdb=yes --vgdb-prefix=./vgdb-prefix-mcinvokeWS7 prereq: test -f vgdb.invoker9 argsB: 10 --vgdb-prefix=./vgdb-prefix-mcinvokeWS --wait=60 -c v.wait 0
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-nlcontrolc3 echo vgdb launched process attached\n4 monitor v.set vgdb-error 9999998 shell ./simulate_control_c --vgdb-prefix=./vgdb-prefix-nlcontrolc 1 grep main nlcontrolc.stderr.out26 shell ./simulate_control_c --vgdb-prefix=./vgdb-prefix-nlcontrolc 1 grep changed nlcontrolc.stdoutB…
97 ln -f -s ../coregrind/vgdb gdbserver_tests/vgdb98 ln -f -s ../../coregrind/vgdb gdbserver_tests/solaris/vgdb102 if gdbserver_tests/vgdb --help 2>&1 |105 rm -f gdbserver_tests/vgdb.invoker107 touch gdbserver_tests/vgdb.invoker
3 # gdbserver must send a signal to itself that is wait-ed for by vgdb.4 # But if this signal is masked, then vgdb does not recuperate the control8 vgopts: --tool=none --vgdb=yes --vgdb-error=0 --vgdb-prefix=./vgdb-prefix-nlsigvgdb10 prereq: test -e gdb -a -f vgdb.invoker
1 # test that vgdb can invoke a process when all threads are in Runnable or Yielding mode5 vgopts: --tool=memcheck --vgdb=yes --vgdb-prefix=./vgdb-prefix-mcinvokeRU7 # as the Valgrind process is always busy, we do not need the vgdb.invoker prereq.11 argsB: 10 --vgdb-prefix=./vgdb-prefix-mcinvokeRU --max-invoke-ms=0 --wait=60 -c v.wait 0
3 # vgdb must queue these signals and deliver them before PTRACE_DETACHing.7 vgopts: --tool=none --vgdb=yes --vgdb-error=0 --vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue9 prereq: test -e gdb -a -f vgdb.invoker
2 # also test the --vgdb-stop-at startup and exit args (so we do not use3 # --vgdb-error=0 here)6 vgopts: --tool=none --vgdb=yes --vgdb-stop-at=startup,exit --vgdb-prefix=./vgdb-prefix-nlgone-exit
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-mcinfcallRU3 echo vgdb launched process attached\n4 monitor v.set vgdb-error 9999998 shell ./simulate_control_c --vgdb-prefix=./vgdb-prefix-mcinfcallRU 1 grep main mcinfcallRU.stderr.o…
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-mcinfcallWSRU3 echo vgdb launched process attached\n4 monitor v.set vgdb-error 99999916 shell ./simulate_control_c --vgdb-prefix=./vgdb-prefix-mcinfcallWSRU 1 grep main mcinfcallWSRU.stde…
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-mcmain_pic3 echo vgdb launched process attached\n5 monitor v.set vgdb-error 999999
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-mssnapshot3 echo vgdb launched process attached\n4 monitor v.set vgdb-error 999999
23 --port of vgdb, and using the tcp/ip variant of the 'target remote'33 Some tests implies to have a vgdb "ptrace invoker" capable.86 progB: another program (typically, either gdb or vgdb standalone)93 So, each test gets its own '--vgdb-prefix' argument.95 if a previous test stayed blocked, the vgdb of the next test154 valgrind --vgdb=yes --vgdb-error=0 --vgdb-poll=500 ./t160 target remote|vgdb162 target remote|vgdb reattach164 target remote|vgdb reattach171 valgrind --vgdb=yes --vgdb-error=1 --vgdb-poll=500 ./t[all …]
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-mcsigpass3 echo vgdb launched process attached\n4 monitor v.set vgdb-error 999999
2 # Note: we need --vgdb=full to stop at the instruction following the watchpoint.6 vgopts: --tool=memcheck --vgdb=full --vgdb-error=0 --vgdb-prefix=./vgdb-prefix-mcwatchpoints
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-mcwatchpoints3 echo vgdb launched process attached\n4 monitor v.set vgdb-error 999999
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-hginfo3 echo vgdb launched process attached\n4 monitor v.set vgdb-error 999999
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-nlgone-return3 echo vgdb launched process attached\n
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-mcbreak3 echo vgdb launched process attached\n4 monitor v.set vgdb-error 99999928 monitor v.set vgdb-error 069 monitor v.set vgdb-error 0
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-nlgone-abrt3 echo vgdb launched process attached\n
2 target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-nlpasssigalrm3 echo vgdb launched process attached\n4 monitor v.set vgdb-error 999999
2 target remote | ../vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-solaris-nlcontrolc3 echo vgdb launched process attached\n4 monitor v.set vgdb-error 9999998 shell ../simulate_control_c --vgdb-prefix=./vgdb-prefix-solaris-nlcontrolc 1 grep main nlcontrolc.s…17 shell ../simulate_control_c --vgdb-prefix=./vgdb-prefix-solaris-nlcontrolc 6 grep CPU nlcontrolc.st…
10 vgopts: --tool=none --vgdb=yes --vgdb-error=0 --vgdb-prefix=./vgdb-prefix-solaris-nlcontrolc12 prereq: test -e ../gdb -a -f ../vgdb.invoker