From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org, palves@redhat.com
Subject: [rfc v2][0/6] Remote /proc file access
Date: Fri, 13 Jan 2012 18:14:00 -0000 [thread overview]
Message-ID: <201201131813.q0DID9r1031719@d06av02.portsmouth.uk.ibm.com> (raw)
Hello,
this is an updated series of patches to implement a generic
"info proc" command that works with remote/gdbserver Linux
targets.
The difference to the earlier version here:
http://sourceware.org/ml/gdb-patches/2011-12/msg00007.html
is that I've implemented Pedro's suggestions to access /proc
via generic file-access primitives instead of using the
target object mechanism.
Some code and ideas from Pedro's prototype here:
http://sourceware.org/ml/gdb-patches/2012-01/msg00353.html
has been integrated into this patch series.
1/6: Distinguish target and "fake" PID values
2/6: Always enable multi-process remote extension if possible
3/6: File I/O target operations
4/6: Readlink as file I/O target operation
5/6: Make "info proc" command generic
6/6: Implement "info proc" on Linux via target file I/O
I've also updated and tested the remote generate-core-file
patch series to use target file I/O instead of TARGET_OBJECT_PROC.
I'll post this once this approach is agreed to.
I've tested this series on i386 native and remote, as well as
on ARM remotely. No regressions; a couple of additional
test cases (info-proc.exp) are now passing.
Any further comments comments on this approach are appreciated!
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next reply other threads:[~2012-01-13 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 18:14 Ulrich Weigand [this message]
2012-01-16 16:39 ` Pedro Alves
2012-01-16 18:27 ` Ulrich Weigand
2012-01-16 19:38 ` Pedro Alves
2012-01-17 19:41 ` Ulrich Weigand
2012-01-17 19:46 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201201131813.q0DID9r1031719@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox