From: Ian Lance Taylor <ian@cygnus.com>
To: kk@ddeorg.soft.net
Cc: ralf@uni-koblenz.de, gas2@cygnus.com, bfd@cygnus.com
Subject: Re: Debugging the GNU Linker on MIPS...
Date: Sat, 06 Feb 1999 08:10:00 -0000 [thread overview]
Message-ID: <199902061605.LAA26156@subrogation.cygnus.com> (raw)
In-Reply-To: <199902060952.PAA09616@bombay.ddeorg.soft.net>
Date: Sat, 06 Feb 1999 15:22:25 +0530
From: "Koundinya.K" <kk@ddeorg.soft.net>
I would like to know how one can debug the linker at source level. I have
not done this type of debugging before. How are there tools usually
debugged. I am not able to figure out how it is possible to debug a linker.
Is there any special way for debugging there ??
The tool you need is called gdb. There's nothing special about the
linker; debugging it is just like debugging any other complex program.
If you've really never used a source level debugger, then you have a
pretty steep learning curve ahead of you.
Ian
prev parent reply other threads:[~1999-02-06 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-06 1:47 Koundinya.K
1999-02-06 8:10 ` Ian Lance Taylor [this message]
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=199902061605.LAA26156@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=bfd@cygnus.com \
--cc=gas2@cygnus.com \
--cc=kk@ddeorg.soft.net \
--cc=ralf@uni-koblenz.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).