This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Should we be able to read simulator memory immediately after a "load" command?

From: Kevin Buettner <kevinb at redhat dot com>
To: gdb-patches at sourceware dot org
Date: Mon, 28 Jun 2010 16:55:14 -0700
Subject: Re: Should we be able to read simulator memory immediately after a "load" command?
References: <20100628130010.360f398d@mesquite.lan> <4C29213C.8020308@vmware.com>

On Mon, 28 Jun 2010 15:25:00 -0700
Michael Snyder <msnyder@vmware.com> wrote:

> Hmm, should we substitute "target_has_memory"?
> 
> Is that set to TRUE after a load?

If default_child_has_memory() is used, which is currently the case for
the remote-sim target, it will not return TRUE after a "load", but
before a "run".

Kevin

Follow-Ups:
- Re: Should we be able to read simulator memory immediately after a "load" command?
  - From: Michael Snyder

References:
- Should we be able to read simulator memory immediately after a "load" command?
  - From: Kevin Buettner
- Re: Should we be able to read simulator memory immediately after a "load" command?
  - From: Michael Snyder

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]