From: Pedro Alves <palves@redhat.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc v2][0/6] Remote /proc file access
Date: Mon, 16 Jan 2012 16:39:00 -0000 [thread overview]
Message-ID: <4F14446F.3060704@redhat.com> (raw)
In-Reply-To: <201201131813.q0DID9r1031719@d06av02.portsmouth.uk.ibm.com>
On 01/13/2012 06:13 PM, Ulrich Weigand wrote:
> Any further comments comments on this approach are appreciated!
I've been through the series, and it looks good to me.
Thanks a lot! If this doesn't work out in the end, I'll certainly help
sort it out.
I've given a couple comments in reply to the patches directly. I'm leaving
some general-ish comments here:
- We could consider making "info proc" work with the default run
target if the current target can't handle it, so that
"info proc PID" works even when not debugging a process yet,
like today.
- It could be argued that the pid parsing should be kept at
the target/gdbarch callbacks side (pass down `char *args'),
so that we didn't have:
+ if (args && *args == '/')
+ tid = strtoul (args + 1, &args, 10);
+ else
+ tid = 0;
in infcmd.c:info_proc_cmd_1 which is only needed by procfs.c.
But please, don't consider these comments blocking in any way.
Thanks again.
--
Pedro Alves
next prev parent reply other threads:[~2012-01-16 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 18:14 Ulrich Weigand
2012-01-16 16:39 ` Pedro Alves [this message]
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=4F14446F.3060704@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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