| Summary: | [remote] Support remote targets with Valgrind | ||
|---|---|---|---|
| Product: | [Tools] Linux Tools | Reporter: | Andrew Overholt <overholt> |
| Component: | Valgrind | Assignee: | Elliott Baron <ebaron> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | aegges, ddykstal.eclipse, mober.at+eclipse |
| Version: | unspecified | ||
| Target Milestone: | 1.0 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | 354342 | ||
| Bug Blocks: | |||
|
Description
Andrew Overholt
This would be interesting to do, and we know there's some user interest in remote profiling. I'll look into it. Perhaps we could make use of RSE. Using TMF may also be useful. My limited understanding of TMF is that you have a small, native agent that sits on the target and facilitates communication with the host. There's an example agent that does a bunch of stuff that we'd probably need. Oops, I said TMF when I meant TCF. The current implementation in trunk needs further attention and will have to wait for a future release. Current problems include not being able to find TCF in any update site (I think this might be a re-namespacing issue), and some program output not being received on the local host. Remote valgrind feature is in master. Please open specific bugs for missing things. |