Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 19:38:00 -0000	[thread overview]
Message-ID: <4F1461F4.6060702@redhat.com> (raw)
In-Reply-To: <201201161728.q0GHSW4D024277@d06av02.portsmouth.uk.ibm.com>

On 01/16/2012 05:28 PM, Ulrich Weigand wrote:
> Pedro Alves wrote:
>> 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.
> 
> Thanks for the review!
> 
>> 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.
> 
> Maybe.  On the other hand, once we've switched to the gdbarch based
> implementation, it would automatically work when not yet debugging
> a process anyway, so I'm not sure this is really necessary ...

Hmm.  I though the target_file_xxx routines would all fail, hitting the default
when no target implement the methods that way.  IOW, I was thinking that we'd
need to pass the struct target_ops pointer down to the gdbarch callback so
the callback could work with the correct target.

-- 
Pedro Alves


  reply	other threads:[~2012-01-16 19:33 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
2012-01-16 18:27   ` Ulrich Weigand
2012-01-16 19:38     ` Pedro Alves [this message]
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=4F1461F4.6060702@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