GDB error messages
Daniel Berlin
dberlin@redhat.com
Fri Aug 4 06:53:00 GMT 2000
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
More information about the Gdb
mailing list