mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 18:13:01 +00:00
81542a63a4
At the beginning of a Valgrind gdbserver test, 2 messages are produced when launching the command target remote | vgdb A message output by vgdb: relaying data between gdb and process <pid> (this message is read by GDB from the vgdb pipe, and re-output on stderr) and a message produced by GDB: Remote debugging using | ./vgdb GDB 8.0 changes the order in which the above messages are output. This causes 2 tests to fail, as the 'relaying' line appears then in a part of the output deleted by a filter script. To avoid this, change the filter scripts to always remove this 'relaying line', which is not particularly interesting to check. All the .exp files containining such a 'relaying' line are updated accordingly. This has been tested with various gdb versions (7.5, 7.7, 7.12, 8.0) on amd64 and/or ppc64. Thanks to Mark Wielaard, which helped to investigate this problem by bisecting the GDB patches in GDB 8.0 causing this change of behaviour. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@16453
52 lines
2.0 KiB
Plaintext
52 lines
2.0 KiB
Plaintext
vgdb-error value changed from 0 to 999999
|
|
Breakpoint 1 at 0x........: file sleepers.c, line 74.
|
|
Continuing.
|
|
Breakpoint 1, sleeper_or_burner (v=0x........) at sleepers.c:74
|
|
74 int i = 0;
|
|
Continuing.
|
|
Breakpoint 1, sleeper_or_burner (v=0x........) at sleepers.c:74
|
|
74 int i = 0;
|
|
Continuing.
|
|
Breakpoint 1, sleeper_or_burner (v=0x........) at sleepers.c:74
|
|
74 int i = 0;
|
|
Continuing.
|
|
Breakpoint 1, sleeper_or_burner (v=0x........) at sleepers.c:74
|
|
74 int i = 0;
|
|
Continuing.
|
|
Program received signal SIGTRAP, Trace/breakpoint trap.
|
|
0x........ in do_burn () at sleepers.c:41
|
|
41 for (i = 0; i < burn; i++) loopnr++;
|
|
[Switching to thread 1 (Thread ....)]
|
|
#0 0x........ in do_burn ()
|
|
41 for (i = 0; i < burn; i++) loopnr++;
|
|
$1 = void
|
|
[Switching to thread 2 (Thread ....)]
|
|
#0 0x........ in syscall ...
|
|
Could not write register "xxx"; remote failure reply 'E.
|
|
ERROR changing register xxx regno y
|
|
gdb commands changing registers (pc, sp, ...) (e.g. 'jump',
|
|
set pc, calling from gdb a function in the debugged process, ...)
|
|
can only be accepted if the thread is VgTs_Runnable or VgTs_Yielding state
|
|
Thread status is VgTs_WaitSys
|
|
'
|
|
[Switching to thread 3 (Thread ....)]
|
|
#0 0x........ in syscall ...
|
|
Could not write register "xxx"; remote failure reply 'E.
|
|
ERROR changing register xxx regno y
|
|
gdb commands changing registers (pc, sp, ...) (e.g. 'jump',
|
|
set pc, calling from gdb a function in the debugged process, ...)
|
|
can only be accepted if the thread is VgTs_Runnable or VgTs_Yielding state
|
|
Thread status is VgTs_WaitSys
|
|
'
|
|
[Switching to thread 4 (Thread ....)]
|
|
#0 0x........ in syscall ...
|
|
Could not write register "xxx"; remote failure reply 'E.
|
|
ERROR changing register xxx regno y
|
|
gdb commands changing registers (pc, sp, ...) (e.g. 'jump',
|
|
set pc, calling from gdb a function in the debugged process, ...)
|
|
can only be accepted if the thread is VgTs_Runnable or VgTs_Yielding state
|
|
Thread status is VgTs_WaitSys
|
|
'
|
|
monitor command request to kill this process
|
|
Remote connection closed
|