Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Gerwyn Davies <gerwynd@tommoll.freeserve.co.uk>
Cc: GDB <gdb@sourceware.cygnus.com>
Subject: Re: GDB error messages
Date: Fri, 04 Aug 2000 06:39:00 -0000	[thread overview]
Message-ID: <398AC769.89CFF86F@cygnus.com> (raw)
In-Reply-To: <002301bffda8$4e0d70e0$ec08883e@gtd-s-machine>

Gerwyn Davies wrote:
> 
> "You can't do that when your target is `exec' " in response to a load
> command.
> 

This one is easy: the load command loads an executable file in the memory of
a remote target, connected via serial port or ethernet to the host where
you are running gdb.

To debug programs on boards and things of a sort one needs a cross debugger.
You need gdb built for your target and the target must have a gdb stub so it
can talk to gdb.


I don't remember when the other one is issued but, judging by the second one, 
it seems that you are not using gdb properly. I would recommend a second pass
through the manual.  If you still have problems after that let us know.


-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299
From dberlin@redhat.com Fri Aug 04 06:53:00 2000
From: Daniel Berlin <dberlin@redhat.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: Gerwyn Davies <gerwynd@tommoll.freeserve.co.uk>, GDB <gdb@sourceware.cygnus.com>
Subject: Re: GDB error messages
Date: Fri, 04 Aug 2000 06:53:00 -0000
Message-id: <m3r9853zf4.fsf@dan2.cygnus.com>
References: <002301bffda8$4e0d70e0$ec08883e@gtd-s-machine> <398AC769.89CFF86F@cygnus.com>
X-SW-Source: 2000-08/msg00034.html
Content-length: 1175

Fernando Nasser <fnasser@cygnus.com> writes:


It means his target isn't defining to_has_exec in the target_ops.
So it doesn't know how to run it.
When I first started the port to BeOS, after I got the config files
set up right so that you could actually compile, these are the
messages you would get if you tried to load and run something.
--Dan

> 
> This one is easy: the load command loads an executable file in the memory of
> a remote target, connected via serial port or ethernet to the host where
> you are running gdb.
> 
> To debug programs on boards and things of a sort one needs a cross debugger.
> You need gdb built for your target and the target must have a gdb stub so it
> can talk to gdb.
> 
> I don't remember when the other one is issued but, judging by the second one, 
> it seems that you are not using gdb properly. I would recommend a second pass
> through the manual.  If you still have problems after that let us know.
> 
> -- 
> Fernando Nasser
> Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com
> 2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
> Toronto, Ontario   M4P 2C9              Fax:  416-482-6299


       reply	other threads:[~2000-08-04  6:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <002301bffda8$4e0d70e0$ec08883e@gtd-s-machine>
2000-08-04  6:39 ` Fernando Nasser [this message]
     [not found]   ` <m3r9853zf4.fsf@dan2.cygnus.com>
2000-08-04  7:05     ` Fernando Nasser

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=398AC769.89CFF86F@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=gerwynd@tommoll.freeserve.co.uk \
    /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