mirror of
git://sourceware.org/git/valgrind.git
synced 2026-01-12 00:19:31 +08: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
59 lines
2.4 KiB
Plaintext
59 lines
2.4 KiB
Plaintext
vgdb-error value changed from 0 to 999999
|
|
Address 0x........ len 10 addressable
|
|
Address 0x........ is 0 bytes inside data symbol "undefined"
|
|
Address 0x........ len 10 defined
|
|
Address 0x........ is 0 bytes inside data symbol "undefined"
|
|
00000000 00000000 0000
|
|
00 00 00 00 00 00 00 00
|
|
0x........: 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........
|
|
00 00
|
|
0x........: 0x........ 0x........
|
|
Address 0x........ len 10 addressable
|
|
Address 0x........ is 0 bytes inside data symbol "undefined"
|
|
Address 0x........ len 10 not defined:
|
|
Uninitialised value at 0x........
|
|
Address 0x........ is 0 bytes inside data symbol "undefined"
|
|
ff00ff00 ff00ff00 ff00
|
|
Address 0x........ len 10 addressable
|
|
Address 0x........ is 0 bytes inside data symbol "undefined"
|
|
Address 0x........ len 10 not defined:
|
|
Uninitialised value at 0x........
|
|
Address 0x........ is 0 bytes inside data symbol "undefined"
|
|
ff000000 0000ff00 ff00
|
|
Address 0x........ len 10 addressable
|
|
Address 0x........ is 0 bytes inside data symbol "undefined"
|
|
Address 0x........ len 10 not defined:
|
|
Uninitialised value at 0x........
|
|
Address 0x........ is 0 bytes inside data symbol "undefined"
|
|
ff00ffff ffffff00 ff00
|
|
Address 0x........ len 2 addressable
|
|
Address 0x........ is 0 bytes inside data symbol "undefined"
|
|
Address 0x........ len 2 not defined:
|
|
Uninitialised value at 0x........
|
|
Address 0x........ is 0 bytes inside data symbol "undefined"
|
|
ff00
|
|
Address 0x........ len 2 not addressable:
|
|
bad address 0x........
|
|
Address 0x........ is 2 bytes inside data symbol "undefined"
|
|
Address 0x........ len 2 not addressable:
|
|
bad address 0x........
|
|
Address 0x........ is 2 bytes inside data symbol "undefined"
|
|
____
|
|
Address 0x........ len 2 has 2 bytes unaddressable
|
|
Address 0x........ len 6 addressable
|
|
Address 0x........ is 4 bytes inside data symbol "undefined"
|
|
Address 0x........ len 6 not defined:
|
|
Uninitialised value at 0x........
|
|
Address 0x........ is 4 bytes inside data symbol "undefined"
|
|
ffffff00 ff00
|
|
Address 0x........ len 10 not addressable:
|
|
bad address 0x........
|
|
Address 0x........ is 0 bytes inside data symbol "undefined"
|
|
Address 0x........ len 10 not addressable:
|
|
bad address 0x........
|
|
Address 0x........ is 0 bytes inside data symbol "undefined"
|
|
0000____ 00000000 0000
|
|
Address 0x........ len 10 has 2 bytes unaddressable
|
|
monitor command request to kill this process
|
|
Remote connection closed
|