From: Mitchell Fang <mitchell.fang@gmail.com>
To: gdb@sourceware.org
Subject: "Load" problem
Date: Mon, 13 Feb 2006 22:08:00 -0000 [thread overview]
Message-ID: <cbd6ac8b0602131408g58e83580p62c0ed3fa7c0df92@mail.gmail.com> (raw)
Has anybody run into this "load" problem before? Looking at the error
message it says it's due to it failing at the function
target_write_memory_partial in symfile.c. The thing I don't get is
whether this error is due to error in transferring the program to the
target or is this something wrong with gdb running on the host
machine? When I look at the remote log file I'm pretty sure that I
wrote the program to memory and returned OK.
A little background on what I'm doing. I'm implementing a GDB stub
thats connect GDB running on a linux machine to a PowerPC4xx eval
board (target) via a JTAG controller.
[mitchell@karla2 testprog]$ ppc_gdb test/testprog
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=ppc-ibm-linux"...
Setting up the environment for debugging gdb.
No symbol table is loaded. Use the "file" command.
No symbol table is loaded. Use the "file" command.
(top-gdb) target remote :8888
Remote debugging using :8888
0x00000000 in ?? ()
(top-gdb) load test/testprog
Loading section .interp, size 0x13 lma 0x80480f4
Memory access error while loading section .interp.
My testprog program is extremely simple.
#include <stdio.h>
#include <stdlib.h>
int main ()
{
int i;
i = 51;
printf("i = %d", i);
return 0;
}
gcc -c -g testprog.c
gcc -o testprog testprog.o
Thanks,
Mitchell
next reply other threads:[~2006-02-13 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 22:08 Mitchell Fang [this message]
2006-02-13 22:22 ` Daniel Jacobowitz
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=cbd6ac8b0602131408g58e83580p62c0ed3fa7c0df92@mail.gmail.com \
--to=mitchell.fang@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