From: Philip Blundell <philb@gnu.org>
To: "Trevor Forbes" <trevorforbes@ozemail.com.au>
Cc: binutils@sources.redhat.com
Subject: Re: Debugging ld
Date: Sun, 26 Aug 2001 02:20:00 -0000 [thread overview]
Message-ID: <E15aw5f-0001h0-00@kings-cross.london.uk.eu.org> (raw)
In-Reply-To: <005d01c12e0e$7fb6a2a0$0300a8c0@ufo>
>I am after a bit of advice. What is the best way to debug ld when building a
>dll using gcc -shared........ I have a test case that does not do the right
>thing
>in linking but I cannot get gdb to trace it through the build process. Its
>gcc
>calling ld that seems to be causing me trouble.
Use "gcc -v" to see what arguments are being passed to ld. Then run ld under
the debugger with the same parameters.
p.
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999 (debian)
iD8DBQE7iL9XVTLPJe9CT30RAh2kAJ9f1el//SY8e6KT9LdKIAHRiYEXRACgm9n7
Rd/HXQeAuq3N8KhOvVbjsXc=
=fTwl
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2001-08-26 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-26 2:06 Trevor Forbes
2001-08-26 2:20 ` Philip Blundell [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=E15aw5f-0001h0-00@kings-cross.london.uk.eu.org \
--to=philb@gnu.org \
--cc=binutils@sources.redhat.com \
--cc=trevorforbes@ozemail.com.au \
/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).