Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Roman Mashak" <romez777@gmail.com>
To: "Roman Mashak" <romez777@gmail.com>, gdb@sourceware.org
Subject: Re: at91sam7 GDB : strange warning
Date: Tue, 03 Jun 2008 00:08:00 -0000	[thread overview]
Message-ID: <40a670230806021708r75711f43l96bbcd4e0e30abd2@mail.gmail.com> (raw)
In-Reply-To: <20080602121659.GA21090@caradoc.them.org>

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 <drow@false.org>:
>> 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


  reply	other threads:[~2008-06-03  0:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02  6:00 Roman Mashak
2008-06-02 12:17 ` Daniel Jacobowitz
2008-06-03  0:08   ` Roman Mashak [this message]
2008-06-02 18:23 ` Michael Snyder

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=40a670230806021708r75711f43l96bbcd4e0e30abd2@mail.gmail.com \
    --to=romez777@gmail.com \
    --cc=gdb@sourceware.org \
    /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