Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	tromey@redhat.com,        gdb-patches@sourceware.org
Subject: Re: [COMMIT] Re: [PATCH] PR gdb/15871: Unavailable entry value is not shown correctly
Date: Fri, 23 Aug 2013 16:50:00 -0000	[thread overview]
Message-ID: <521792EA.3050703@redhat.com> (raw)
In-Reply-To: <5216B5C9.3010402@codesourcery.com>

On 08/23/2013 02:07 AM, Yao Qi wrote:

> I'd like to write this down in section "Internals" in 
> http://sourceware.org/gdb/wiki/ProjectIdeas , let me know what do you think.
> 
> Use target_xfer_error instead of errno.  Some xfer_memory functions 
> (such as target_read_memory and deprecated_xfer_memory) are
> using errno to indicate any error occurs.  This limites what we can 
> return here, because we can't return some GDB-specific errors, such as 
> <unavailable>.  If we need to indicate an errno, bfd error for example, 
> a new TARGET_XFER_E_BFD can be added to target_xfer_error.  See
> http://sourceware.org/ml/gdb-patches/2013-08/msg00589.html for more info.

Thanks, but rather than end up with an incomplete transition,
I went ahead and did the legwork:

 http://sourceware.org/ml/gdb-patches/2013-08/msg00687.html

deprecated_xfer_memory should just be eliminated.  I've now
cleaned up remote.c:

  http://sourceware.org/ml/gdb-patches/2013-08/msg00668.html

A few more to go still ...

$ grep "deprecated_xfer_memory.*=" *.c | grep -v target.c
darwin-nat.c:  darwin_ops->deprecated_xfer_memory = darwin_xfer_memory;
gnu-nat.c:  t->deprecated_xfer_memory = gnu_xfer_memory;
go32-nat.c:  go32_ops.deprecated_xfer_memory = go32_xfer_memory;
monitor.c:  monitor_ops.deprecated_xfer_memory = monitor_xfer_memory;
nto-procfs.c:  procfs_ops.deprecated_xfer_memory = procfs_xfer_memory;
procfs.c:  t->deprecated_xfer_memory = procfs_xfer_memory;
remote-m32r-sdi.c:  m32r_ops.deprecated_xfer_memory = m32r_xfer_memory;
remote-mips.c:  mips_ops.deprecated_xfer_memory = mips_xfer_memory;
remote-sim.c:  gdbsim_ops.deprecated_xfer_memory = gdbsim_xfer_inferior_memory;
windows-nat.c:  windows_ops.deprecated_xfer_memory = windows_xfer_memory;

-- 
Pedro Alves


  reply	other threads:[~2013-08-23 16:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13  7:41 [PATCH 0/2] Test case on entry values Yao Qi
2013-08-13  7:41 ` [PATCH 1/2] Test case for " Yao Qi
2013-08-20 17:39   ` Tom Tromey
2013-08-21  5:55     ` Yao Qi
2013-08-21 15:02       ` Tom Tromey
2013-08-22  0:12         ` Yao Qi
2013-08-22 14:05           ` Tom Tromey
2013-08-23  0:27             ` Yao Qi
2013-08-23 19:23               ` Tom Tromey
2013-08-24  1:56                 ` Yao Qi
2013-08-30 14:52   ` Vidya Praveen
2013-08-30 15:29     ` Vidya Praveen
2013-08-31  0:22       ` Yao Qi
2013-09-10 15:30         ` Vidya Praveen
2013-09-10 23:44           ` Yao Qi
2013-09-11 13:27             ` Vidya Praveen
2013-08-13  7:41 ` [RFC 2/2] Test entry values in trace frame Yao Qi
2013-08-20 17:48   ` Tom Tromey
2013-08-21  6:06     ` Yao Qi
2013-08-21 14:35       ` [PATCH] PR gdb/15871: Unavailable entry value is not shown correctly Pedro Alves
2013-08-21 14:47         ` Mark Kettenis
2013-08-21 15:32           ` Pedro Alves
2013-08-21 15:43             ` Mark Kettenis
2013-08-22  1:25             ` Yao Qi
2013-08-22 10:04               ` [COMMIT] " Pedro Alves
2013-08-23  1:08                 ` Yao Qi
2013-08-23 16:50                   ` Pedro Alves [this message]
2013-08-23  0:32       ` [RFC 2/2] Test entry values in trace frame Yao Qi
2013-08-23 17:04         ` Pedro Alves
2013-08-23 19:16           ` Tom Tromey
2013-08-24  1:56             ` Yao Qi

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=521792EA.3050703@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=tromey@redhat.com \
    --cc=yao@codesourcery.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