History log of /external/valgrind/coregrind/vgdb.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
c42f255524f0bf498e4c46644c60a4cbda3b7997 28-May-2015 Dmitriy Ivanov <dimitry@google.com> Fix x86_64 target build

Bug: http://b/21471495
Bug: https://bugs.kde.org/id=348342
Change-Id: I5b48491d18ced37c9ecff60661fb4a5b47519219
(cherry picked from commit 22bcca76a224404fa81fff26437d15f17be56fd4)
/external/valgrind/coregrind/vgdb.c
5cbcd62afb84cffe8d1130b0b896bd36fab20a05 21-Dec-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix a typo, introduced when fixing a typo.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14829 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
be314cf4423fe5d78224df4d6414471aa395eb0a 21-Dec-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix typo


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14828 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
345affe06343cf6ed038f9d82fceb9b1ea3354b6 21-Dec-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Follow up to rev 14823: make errors when reporting command line non critical
(as e.g. cmdline reporting is not available on MacOS)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14827 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
b7742ab1b3859ebf0d102001745e697725555017 19-Dec-2014 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix a buffer overflow (in case read had returned 1000).
Write out the whole command line.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14823 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
e6460fa595b0bfe3551b378b105140564aaca8d7 04-Nov-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Unmask all signals in vgdb, as the process that launches vgdb
might have masked some.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14691 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
26ed419d60369d0545510eba0832566e24452e1e 04-Nov-2014 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Adds initial support for AArch64 (arm64) on Android. Small programs
(/system/bin/ls, /system/bin/date) run. Still to do:

* enable more malloc/free intercepts

* enable wrappers for ashmem and binder syscalls

* check to see if any special ioctl support is required for ARM Mali GPUs



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14690 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
511df4ecbd147628cb33f556e34d4c0dbfbff51a 12-Sep-2014 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> When piecing together the file name of a vgdb FIFO do not allow
user names and host names containing '/' characters.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14526 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
def5aae79084c7b1128674105f9e657e2af0d5dc 09-Jul-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Rollback the (functional) effect of 13944 and 14134
Re-opening the FIFO before closing it gives (difficult to understand)
problems => rollback the change that keeps the FIFO opened.
Rather handle the race condition by retrying at vgdb side.
See extensive comments in remote-utils.c



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14147 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
6654de8547d2e420c20e21980669b807aa80710e 16-Apr-2014 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> vgdb must not transmit signals when gdbserver has been ptrace-invoked.

Most of the time, Valgrind masks async signals, and polls for such
signals at regular interval.
There is a very narrow range of code (around client syscall logic)
where such signals are unmasked (as they must be able to interrupt
syscalls).
This is the only range of code where Valgrind is expecting to
receive such a signal.

When gdbserver is ptraced invoked, Valgrind is artificially made
to jump out of this code portion. Signals are not masked.
When ptraceing valgrind, vgdb will get these signals but cannot
transmit them immediately, otherwise they arrive in range
of code where they are not expected (causing internal error
in syscall logic) and/or causing gdbserver syscalls to be
interrupted.

3 solutions to solve that were looked at:
1. have the gdbserver code masking signals "as quickly as possible".
Easy to implement, but this leaves still a small window
of code where signals are not masked and would cause a problem.
2. have vgdb setting the SIGMASK of valgrind before invoking
gdbserver.
This would be easy to implement, but changing the SIGMASK
of the ptrace-d process is only available on very recent kernels.
3. have vgdb queuing signals, and only transmitting them once
gdbserver invocation is finished.
This 3rd solution has been implemented.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13896 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
9c6b05db45362b1afb981aa8298ab12ab4027b1a 27-Dec-2013 dejanj <dejanj@a5019735-40e9-0310-863c-91ae7b9d1cf9> mips32: Adding mips32/Android support to Valgrind.

Necessary changes to Valgrind to support mips32 on Android.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13767 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
3c761f0f0344757ac243c65511392fb41d1c841a 01-Dec-2013 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix 326462 Refactor vgdb to isolate invoker stuff into separate module

vgdb.c contained (conditionally compiled) "invoker" code to have ptrace syscalls
used to allow gdb/vgdb to connect to a valgrind process blocked in a syscall.
This "invoker" code is ptrace based.
Not all platforms are using ptrace.
=> refactor vgdb so as allow invoker code to be added more cleanly
for non ptrace based platforms (e.g. Darwin, Solaris).

* add file vgdb.h for:
- definition of the vgdb-invoker interface
- common declarations between vgdb.c and vgdb-invoker implementations
* move ptrace related code from vgdb.c to new file vgdb-invoker-ptrace.c
* new file vgdb-invoker-none.c containing an empty invoker implementation
used on platforms that do not (yet) have a invoker implementation
(e.g. android and darwin).
* modified Makefile.am to use one of the vgdb-invoker-*.c file depending
on the platform.
* small changes related to changing ptraceinvoker to invoker in various files:
gdbserver_tests/make_local_links, gdbserver_tests/nlcontrolc.vgtest,
gdbserver_tests/mcinvokeRU.vgtest, gdbserver_tests/nlsigvgdb.vgtest
gdbserver_tests/mcinvokeWS.vgtest, coregrind/m_gdbserver/README_DEVELOPERS

Patch from Ivo Raisr, slightly modified



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13743 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
0f157ddb404bcde7815a1c5bf2d7e41c114f3d73 18-Oct-2013 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update copyright dates (20XY-2012 ==> 20XY-2013)


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13658 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
50c207584610c860320b6152a59e2217daaa8d18 22-Aug-2013 dejanj <dejanj@a5019735-40e9-0310-863c-91ae7b9d1cf9> mips32: Fix a problem with gdb invoker.

This patch fixes the endian issue with gdb invoker on mips32
big endian. Now we are using pointer to long long and
we don't need to sign extend registers. On mips32 o32 abi
we need to make extra stack space when we are calling
function.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13507 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
5507d226fd83f2dcf9c5552787e8114594c9972f 06-Aug-2013 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> fix --vgdb-prefix no / character interpreted differently by V gdbsrv and vgdb
When --vgdb-prefix contains no / character,
the Valgrind gdbsrv is interpreting the prefix value as the filename
prefix in the current directory, while vgdb interprets this as
a directory to be opened in the current directory.

Cbange vgdb.c so that it uses the same interpretation as V gdbsrv



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13485 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
4e98f7ce0dde3d4295078cfc5fc4cb6ea06e87bd 03-Aug-2013 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update configure machinery to detect PTRACE_GETREGS
Using #ifdef PTRACE_GETREGS gives difficulties as in some
platforms (e.g. mips) PTRACE_GETREGS is not defined as a
preprocessor symbols unless linux/ptrace.h is included.
However, including linux/ptrace.h causes compilation error on some
other platforms

=> better detect that PTRACE_GETREGS can be used using the
configure machinery.

This should make vgdb PTRACE_GETREGS working again on
various platforms (x86/amd64/mips/...) as PTRACE_GETREGS
was disabled on all of these following r13471



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13482 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
f1f5ce00cc3814ff565ab3074dd920c0e5ec91bb 25-Jul-2013 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> do not include linux/ptrace.h in vgdb.c

Include of linux/ptrace.h was added in revision r11740,
to avoid compilation error on s390x (fedora and suse).

The compilation error was retrieved thanks to archeological research
done by Christian Borntraeger: without this include, the following was given:
error: 'PT_ENDREGS' undeclared
There was also some errors on ppc64 around the same time:
error: 'PTRACE_GETREGS' undeclared

Currently, the inclusion of linux/ptrace.h gives a problem on amd64/fedora20:
/usr/include/linux/ptrace.h:58:8: error: redefinition of ‘struct ptrace_peeksiginfo_args’
/usr/include/sys/ptrace.h:191:8: note: originally defined here

According to man ptrace, it is good enough to include sys/ptrace.h
(which should avoid the problem on amd64/f20).

The linux/ptrace.h is deemed not necessary anymore as:
1. Christian has tested on sles11sp2 on s390x.
2. since linux/ptrace.h was added in vgdb.c, #ifdef PT_ENDREGS and
#ifdef PTRACE_GETREGS were added

=> remove the linux/ptrace.h
(tested on x86/f12, ppc64/f18, amd64/deb6, sles11sp2/s390x)

Thanks to Christian for the investigations



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13471 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
25583179757e4393a687330732675e3c63c0e0d1 09-May-2013 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> fix 319235 --db-attach=yes is broken with Yama ptrace scoping enabled
On Ubuntu systems, ptrace_scoping could forbid a process to ptrace another.
This ptrace scoping was already handled for vgdb by using SET_PTRACER
(the valgrind process must be ptraced by vgdb when it is blocked
in a syscall).
set_ptracer is however also needed when the old mechanism --db-attach=yes
is used.
The following changes are done:
* make the set_ptracer logic callable outside gdbserver
* make set_ptracer less restrictive (i.e. allow all
processes of the user to ptrace). This removes a limitation for vgdb.
* call the set_ptracer in the child launched for --db-attach=yes
* cleaned up the ptrace scope restriction message and doc as vgdb
is now working properly by default, even with ptrace_scope enabled.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13384 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
4df0bfc0614379192c780c944415dc420d9cfe8e 28-Feb-2013 petarj <petarj@a5019735-40e9-0310-863c-91ae7b9d1cf9> mips: adding MIPS64LE support to Valgrind

Necessary changes to Valgrind to support MIPS64LE on Linux.
Minor cleanup/style changes embedded in the patch as well.
The change corresponds to r2687 in VEX.
Patch written by Dejan Jevtic and Petar Jovanovic.

More information about this issue:
https://bugs.kde.org/show_bug.cgi?id=313267


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13292 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
36c01ef411ad2c71d396a024fdeb506aebd1cd7c 16-Jan-2013 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Improve error handling when vgdb cannot read process cmd line



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13233 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
3e7986312a0ffc7646b0552d4c4ea3744a870e73 24-Nov-2012 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix some casts that removed const-ness as pointed out by
GCC's -Wcast-qual.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13138 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
6bd9dc18c043927c1196caba20a327238a179c42 23-Nov-2012 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Changes to allow compilation with -Wwrite-strings. That compiler option
is not used for testcases, just for valgrind proper.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13137 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
adfb8a704c763eb6f8c3e8e79b17322d6c46b040 01-Nov-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Ensure vgdb.c is warningless with -Wpointer-sign
* use normal 'char' (when possible) rather than 'unsigned char'
* fix bug in case a character val >= 128 is given in a -c command



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13098 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
66bc6e53d12d6d107eab3bebcfc814ff5179d1dc 31-Oct-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> for debuglevel >=2, ensure write_buf debug output only writes the req nr of char


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13096 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
6dda089df8ac11ce51e1e783bebd05ebb9c90a1d 18-Aug-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> fix n-i-bz vgdb ptrace calls wrong on mips, causing blocked syscalls to fail

(patch from Petar Jovanovic).

The mips specific code of vgdb.c was storing the arguments
at wrong places in the ptrace setreg. This caused the blocked syscall(s)
to return with an error rather than to be properly restarted.
With this commit, the gdbsrv tests are not blocking anymore
with Valgrind mips32 running on mips64 GNU/Linux.
vgdb is believed to be functional, even if process is blocked in a syscall.

The following tests are still failing
gdbserver_tests/mcbreak (stdout)
gdbserver_tests/mcbreak (stdoutB)
gdbserver_tests/mcbreak (stderrB)
gdbserver_tests/mcsignopass (stderr)
gdbserver_tests/mcsignopass (stdoutB)
gdbserver_tests/mcsigpass (stderr)
gdbserver_tests/mcsigpass (stdoutB)
gdbserver_tests/nlcontrolc (stdoutB)
gdbserver_tests/nlsigvgdb (stderr)
gdbserver_tests/nlsigvgdb (stderrB)

Of the above, nlsigvgdb failure is still strange.
Others looks like "normal" differences due e.g. to mips specific gdb
behaviour and/or none/tests/faultstatus (re-used in gdbsrv tests)
behaving differently on mips.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12881 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
03f8d3fc25f5a45c5826259d1b33b7f310117279 05-Aug-2012 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Update copyright dates to include 2012.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12843 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
5d5dd8e6b7ff782fc89f5b96cecf04839742882b 05-Aug-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> 301265 - add x86 support to Android build

Patch by Dragos Tatulea.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12835 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
0e3e768c2b32ff557a5e261fe0606e4354679655 10-Jun-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Avoid unused warning for ptrace_write_memory in vgdb.c (only used on some platforms)


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12630 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
5db15403e889d4db339b342bc2a824ef0bfaa654 07-Jun-2012 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Merge in a port for mips32-linux, by Petar Jovanovic and Dejan Jevtic,
mips-valgrind@rt-rk.com, Bug 270777.

Valgrind: changes to existing files.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12616 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
8fb1b13fa096fd6e205e02452ac873e56b9f9e73 13-Apr-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix 297992 Support systems missing WIFCONTINUED (e.g. pre-2.6.10 Linux)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12503 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
bb4827b2ba7d03fc3d33fa657162d53b68cbdfe9 06-Apr-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> fix off by one in string



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12493 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
ae52a9398788dfa1b4d51b03013e8665268ad6df 13-Jan-2012 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> Valgrind gdbserver can open/close connections multiple times
=> avoid leak when re-computing the default vgdb prefix.
Similar change in vgdb.c


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12328 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
1d76a80d63502951cb9cbf6f696d663f093083fa 26-Dec-2011 philippe <philippe@a5019735-40e9-0310-863c-91ae7b9d1cf9> fix 289699 vgdb connection in relay mode erroneously closed due to buffer overrun
* use PBUFSIZ+1 for buffers reading characters from gdbserver:
vgdb reads up to PBUFSIZ characters from gdbserver.
If vgdb receives a burst of packet from Valgrind gdbserver, PBUFSIZ
characters can be read. The tracing code adds a trailing \0 to
this buffer => to avoid buffer overrun, the buffers are dimensionned
with PBUFSIZ+1.
* use read_buf in function read_char, rather than directly calling read.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12319 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
992d3cc883bd5ee2da28f2a9c307cc006cb1768b 22-Oct-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Make vgdb.c work on Android, so that the GDB server as a whole
will work on Android. Fixes #283600.
(Philippe Waroquiers, philippe.waroquiers@skynet.be)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12204 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
ab8630fd1c559a3d8a3e429cf8e9f2e4b94a3ff6 29-Sep-2011 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Change the name of the pipes for vgdb by adding username and hostname.
Those are obtained by looking at some commonly defined environment
variables.
That should help with problems where /tmp is shared or process IDs get
recycled. We had some intermittent nightly build issues because of that.
Partial fix for bugzilla #280757.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12071 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
b985e2de52983cafd2d17cc6c9e60064847777fd 29-Sep-2011 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Remove hardwired /tmp directory in vgdb. Honour VG_TMPDIR
and TMPDIR which was introduced when fixing bugzilla #267020.
Factor out VG_(tmpdir). New function VG_(vgdb_path_prefix).
Partially fixes bugzilla #280757.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12063 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
e7f8f3f669763ac7b4f83428771f563ba55d74e2 12-Jul-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Reinstate inclusion of signal.h, removed in r11886.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11891 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
56501b67e44eb4d012449e16aafe49d885b557f1 12-Jul-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Reinstate inclusion of unistd.h, removed in r11886.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11890 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
cbe385015145f16e3e88f919d8979df628a535ea 12-Jul-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix Linux build breakage caused by header rearrangement in r11885, sigh.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11886 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
0ba37c90c4674515da387b30a6e5f23fa75a173c 12-Jul-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Build system fixes so as to temporarily disable the GDBserver on
Android. Making that work will require a bit of extra effort due to
minor glibc-vs-bionic differences.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11885 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
30b3eca94e609214d9ac8dabfee9be3f3ab46d85 28-Jun-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> valgrind and tool mon. cmds prefixes changes + doc fixes + new vgdb option
--cmd-time-out

* changed prefixes of Valgrind core monitor commands from vg. to v.
* removed prefixes of Tool monitor commands
* memcheck leak_check 'leakpossible' arg renamed to 'possibleleak'
* memcheck make_memory 'ifaddressabledefined' arg renamed to
'Definedifaddressable'
(with uppercase D to avoid confusion with 'defined' arg).
* vgdb options
- Some doc updates : more logical option order documentation,
specify 'standalone' for options aimed at standalone usage.
- added option --cmd-time-out for standalone vgdb
(comment of Josef Weindendorfer, needed to interface with a callgrind GUI)
* updated tests according to the above.
* updated documentation according to the above.
* some additional minor doc fixes/clarifications

(Philippe Waroquiers, philippe.waroquiers@skynet.be). Bug 214909
comment 111.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11844 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
b2572b52b37d56d302408395f7fed9f509423af1 26-Jun-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> GDB server:
* Fix bug in logic related to signal-passing
* use SIGSTOP instead of SIGTRAP (avoid race condition)
(Philippe Waroquiers, philippe.waroquiers@skynet.be). Bug 214909
comment 109.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11837 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
1568e17cf07007c677274ce877973c7ed9357df2 18-Jun-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Minor GDBserver source tidying. Also a small usability fix: if
--vgdb-error=N is specified, print a bit of text telling the user the
magic commands to give GDB in order to attach to the process.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11822 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
d142f99836471d4245250247cc9ac7bc5a1391fa 17-May-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> gdbserver: misc fixes (#214909 c 77)
Fix some tests on ppc-debian6,s390x + handled Nick Nethercote, Josef
Weidendorfer comments

* improved testing & related doc
- added option --vex-iropt-precise-memory-exns=yes to mcsig(no)pass.vgtest
+ updated manual-core.xml
- cleanup some comments in *.vgtest
- modified filter_gdb and filter_memcheck_monitor to
handle specific ppc/debian6.0 mcsig(no)pass output
handle specific s390x 'missing debug info'
- added more information in README_DEVELOPPERS on how to
investigate failing gdbserver tests.

* handled Nick Nethercote comment:
Replaced kludgy ms.snapshot detailed
by ms.detailed_snaphot
Updated documentation and test.

* handled Josef Weindendorfer comments:
- do not report an error if ptrace_scope file can't be read.
Instead, a debug trace is done if -d (debug) option given
- added an option -l to give the list of active Valgrind
gdbserver. Useful a.o. to support callgrind_control.
Updated documentation
- added ref. to vgdb help in the vgdb --help message

(Philippe Waroquiers, philippe.waroquiers@skynet.be)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11770 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
d8c12f178d9d03b934ce10d6fcb45c27503889dc 12-May-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> * fixed two bugs reported by the IBM BEAM checker:
fd leak in vgdb.c
break missing in valgrind-low-s390x.c

* use option --vgdb=full for the tests mcsigpass.vgtest and mcsignopass.vgtest
This might improve these tests on ppc32/debian 6.0

* added a paragraph in gdbserver_tests/README_DEVELOPPERS to indicate
how to report problems about failing gdbserver tests.

(bug 214909 comment 71, Philippe Waroquiers, philippe.waroquiers@skynet.be)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11748 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
eefeeb7a60a347bc851605fadd52672cbd927201 10-May-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Improvements for testing and compilation breakage for the GDB server
on various platforms:

* In all gdbserver_tests using gdb:
Made a more general way to remove the initial start message.

* tests using threads burning cpu modified to have only 1 thread.
This makes them independent of the scheduler fairness.

* filter_gdb and filter_vgdb enhanced to anonymise
some debian 6.0/ppc specific things
some s390x/gdb 7.0, gdb 7.1 specific things

* vgdb.c: added an #include <linux/ptrace.h> to fix compilation
on s390x fedora and suse. (Christian Boerntrager)

* fixed a bug in valgrind-low.c debug log :
when a register size is 0, its image cannot be output (and register
should not be transferred).

* added a parameter --keep-unfiltered to vg_regtest.in
This will make it easier to update filter_gdb:
in case gdbserver_tests are failing due to "artificial"
differences to be filtered, re-run the tests using:
perl tests/vg_regtest --keep-unfiltered gdbserver_tests
Then a tar file with all the *.out in gdbserver_tests
will allow me to better/faster update the filter_gdb.

* made a better detection of a working PTRACE_GETREGS at compile time
and/or at run-time.

This is the patch on bug 214909 comment 69.
(Philippe Waroquiers, philippe.waroquiers@skynet.be)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11740 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c
3b290486cd4cd601b20e04340e593c9ed9717e5f 06-May-2011 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Implement a GDB server in Valgrind. See #214909.
(Philippe Waroquiers, philippe.waroquiers@skynet.be)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11727 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/coregrind/vgdb.c