From: libra <mr924352@cs.nthu.edu.tw>
To: gdb@sources.redhat.com
Subject: About bfd in gdb
Date: Sun, 04 Jul 2004 13:35:00 -0000 [thread overview]
Message-ID: <1088948153.40e807b9434db@webmail.cs.nthu.edu.tw> (raw)
Hello,all:
About the gdb source code, I have some questions.
I will use "ARM" for my example.
In the gdb source code architecture,when you build the gdb(ex: target=arm-efl)
,you can find that first you will build bfd and opcodes that the same as
binutils, then build the gdb and sim.
My question is that :
Why we must build the bfd and opcodes parts that the same as in binutils (like
archures.c reloc.c arm-dis.c and arm-opc.h and so on)
My idea is that :
We just need to build bfd inoder to recognize the input file format,then
i can use the gdb to connect to simulator(sim),after that, I can run my own
program.
So, the aboved mentioned file (ex: arm-dis.c and arm-opc.h), why is those file
must be built again. It seem does not be used in gdb.
thanks a lot!!
next reply other threads:[~2004-07-04 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 13:35 libra [this message]
2004-07-04 14:00 ` Ramana Radhakrishnan
2004-07-05 1:59 libra
2004-07-08 21:52 ` Andrew Cagney
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=1088948153.40e807b9434db@webmail.cs.nthu.edu.tw \
--to=mr924352@cs.nthu.edu.tw \
--cc=gdb@sources.redhat.com \
/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