From: Robert Plantz <plantz@sonoma.edu>
To: Kenton Brede <kbrede@gmail.com>
Cc: linux-assembly@vger.kernel.org
Subject: Re: suffix or operands invalid for
Date: Fri, 22 Dec 2006 11:15:58 -0800 [thread overview]
Message-ID: <1166814958.4573.64.camel@localhost> (raw)
In-Reply-To: <d5418ffc0612221105p2b6803b5ta9a871c6d924972a@mail.gmail.com>
On Fri, 2006-12-22 at 13:05 -0600, Kenton Brede wrote:
> I tried that and the output of gcc gave me enough information that I
> was able to get the prog to compile on the system.
Another program you may find useful is
objdump -d myProg
where "myProg" is the name of your executable. This will give you a
disassembled view of your program as it looks in memory. You can see
where the external library functions are called, etc. It's a long
display, so pipe it through more or less.
next prev parent reply other threads:[~2006-12-22 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 2:39 suffix or operands invalid for Kenton Brede
2006-12-22 12:51 ` Frank Kotler
2006-12-22 14:18 ` Kenton Brede
2006-12-22 16:16 ` Robert Plantz
2006-12-22 16:55 ` Robert Plantz
2006-12-22 19:05 ` Kenton Brede
2006-12-22 19:15 ` Robert Plantz [this message]
2006-12-31 18:06 ` Hendrik Visage
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=1166814958.4573.64.camel@localhost \
--to=plantz@sonoma.edu \
--cc=kbrede@gmail.com \
--cc=linux-assembly@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).