From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3135 invoked by alias); 3 Jun 2008 00:08:38 -0000 Received: (qmail 3123 invoked by uid 22791); 3 Jun 2008 00:08:36 -0000 X-Spam-Check-By: sourceware.org Received: from py-out-1112.google.com (HELO py-out-1112.google.com) (64.233.166.178) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 03 Jun 2008 00:08:05 +0000 Received: by py-out-1112.google.com with SMTP id a77so664561pyh.33 for ; Mon, 02 Jun 2008 17:08:03 -0700 (PDT) Received: by 10.142.72.21 with SMTP id u21mr3817848wfa.65.1212451682630; Mon, 02 Jun 2008 17:08:02 -0700 (PDT) Received: by 10.142.125.1 with HTTP; Mon, 2 Jun 2008 17:08:02 -0700 (PDT) Message-ID: <40a670230806021708r75711f43l96bbcd4e0e30abd2@mail.gmail.com> Date: Tue, 03 Jun 2008 00:08:00 -0000 From: "Roman Mashak" To: "Roman Mashak" , gdb@sourceware.org Subject: Re: at91sam7 GDB : strange warning In-Reply-To: <20080602121659.GA21090@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <40a670230806012259t35ed6238yafe779f1cf190af9@mail.gmail.com> <20080602121659.GA21090@caradoc.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-06/txt/msg00004.txt.bz2 You were right, the mesage was caused by a mistyped line in .gdbinit. I have some misunderstanding on how images are loaded in GDB. Say the simplest .gdbinit looks like this: target remote localhost:2331 load and gdb is run: #gdb my_image.elf This results in error: .gdbinit:2: Error in sourced command file: No executable file specified. Use the "file" or "exec-file" command. (gdb) If remove 'load' line from .gdbinit, then no problem to load an image from GDB console and no need to specify image name, provided that it was passed to gdb as parameter. Is it expected behavior of GDB? Is there any way to have GDB to load images from .gdbinit without specifying image names, as they may differ from case to case. 2008/6/2 Daniel Jacobowitz : >> Application is being debugged and run perfectly, without significant >> issues. I only wonder the root of that warning. I googled for it, but >> with no luck. Hope someone here will give a hint. > > It is probably produced by some command in your .gdbinit file. You > should figure out which one; then it will probably be clear what the > problem is. > -- Roman