[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [linuxtools-dev] Remote Valgrind
|
Hi Marc,
This is interesting work and could be used in conjunction with the
remote work being done or as an alternative to it.
The remote tools work is attempting to unify the tools so that there is
only one server needed on the remote machine. Currently, there is a
central method for running commands and accessing files on the remote
system via RSE, or TCF via RSE (i.e. you can have a TCF or RSE server
running remotely).
The current Valgrind remote launch sends the executable to the remote
system and starts Valgrind there, outputs the data to a remote file,
then shuttles the data file back for processing locally.
Whether the data is still output when Valgrind is running in the special
gdbserver mode, I do not know at this time. If it does get generated,
then Valgrind could still generate the chart data and one could use gdb
to control the Valgrind run.
Alternatively, one could simply start Valgrind in the special mode on
the remote system and use gdb to access it locally and by-pass the
remote Valgrind launcher altogether.
-- Jeff J.
On 11/08/2011 02:10 PM, Marc Khouzam wrote:
Hi,
there has been a lot of interest on using Linux Tools towards a
remote target. I haven't followed the discussions in all their
details so I'm not sure if the following has been mentioned before.
It was brought to my attention that the very recent release of
Valgrind has some remote support through GDB. I thought this
may be of interest to the people involved. Maybe re-using CDT's
GDB integration could be an easy solution to control Valgrind.
Valgrind 3.7.0 Released (5 November 2011)
http://valgrind.org/docs/manual/dist.news.html
Some changes..:
====
* GDB server: Valgrind now has an embedded GDB server. That means it
is possible to control a Valgrind run from GDB, doing all the usual
things that GDB can do (single stepping, breakpoints, examining
data, etc). Tool-specific functionality is also available. For
example, it is possible to query the definedness state of variables
or memory from within GDB when running Memcheck; arbitrarily large
memory watchpoints are supported, etc. To use the GDB server, start
Valgrind with the flag --vgdb-error=0 and follow the on-screen
instructions.
====
Marc
_______________________________________________
linuxtools-dev mailing list
linuxtools-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev