From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25277 invoked by alias); 22 Feb 2006 18:18:19 -0000 Received: (qmail 25202 invoked by uid 22791); 22 Feb 2006 18:18:19 -0000 X-Spam-Check-By: sourceware.org Received: from sadr.equallogic.com (HELO sadr.equallogic.com) (66.155.203.134) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 22 Feb 2006 18:18:16 +0000 Received: from sadr.equallogic.com (localhost.localdomain [127.0.0.1]) by sadr.equallogic.com (8.12.8/8.12.8) with ESMTP id k1MIIETW009183 for ; Wed, 22 Feb 2006 13:18:14 -0500 Received: from M31.equallogic.com (M31.equallogic.com [172.16.1.31]) by sadr.equallogic.com (8.12.8/8.12.8) with SMTP id k1MIIEGF009178; Wed, 22 Feb 2006 13:18:14 -0500 Received: from pkoning.equallogic.com ([172.16.1.169]) by M31.equallogic.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 22 Feb 2006 13:18:05 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17404.43748.408821.118787@gargle.gargle.HOWL> Date: Wed, 22 Feb 2006 18:38:00 -0000 From: Paul Koning To: drow@false.org Cc: gdb@sourceware.org Subject: Re: Does GDB use VMA addresses when uploading an image to debug in a remote target? References: <1140631963.8331@satelite.dea.inpe.br> <20060222181146.GA28251@nevyn.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00297.txt.bz2 >>>>> "Daniel" == Daniel Jacobowitz writes: Daniel> I recently encountered this problem in another context, where Daniel> the stub did support reflashing; so maybe GDB needs to be Daniel> more flexible about it. I'm not sure. Yes, that would be useful. There are other examples for LMA != VMA where LMA is the correct load address. For example: 1. LMA is an available memory area, VMA is "low memory", and a bit of initialization code moves the loaded code to low memory. It can't be loaded directly there because there is currently running code already there, and loading on top of it will crash the system. 2. LMA is an unmapped address, VMA is a mapped address. The loader doesn't know about mapping. The init code turns on the mapping, at which point execution continues via VMA. We do #2 in our embedded system. So this suggests that an option to load at LMA would be useful. paul