From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23538 invoked by alias); 21 Oct 2008 22:18:01 -0000 Received: (qmail 23500 invoked by uid 71); 21 Oct 2008 22:18:01 -0000 Date: Tue, 21 Oct 2008 22:18:00 -0000 Message-ID: <20081021221801.23499.qmail@sourceware.org> To: nobody@sources.redhat.com Cc: gdb-prs@sources.redhat.com, From: Daniel Jacobowitz Subject: Re: gdb/2540: GDB needs a --sysroot command line option Reply-To: Daniel Jacobowitz Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2008-q4/txt/msg00022.txt.bz2 The following reply was made to PR gdb/2540; it has been noted by GNATS. From: Daniel Jacobowitz To: psmith@gnu.org Cc: gdb-gnats@sources.redhat.com Subject: Re: gdb/2540: GDB needs a --sysroot command line option Date: Tue, 21 Oct 2008 18:12:53 -0400 On Tue, Oct 21, 2008 at 09:59:56PM -0000, psmith@gnu.org wrote: > Even if I try something like "gdb -ex 'set sysroot ...' " it won't help, because GDB will internalize the executable and core before running the set sysroot command. I think that this is the actual bug; we should have a way to run commands before or after loading. I usually work around it with this awkward form: gdb -ex 'set sysroot ...' -ex 'core-file core' -- Daniel Jacobowitz CodeSourcery