public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Show Symbol Table for OMF (.obj)?
Date: Mon, 16 May 2016 19:42:00 -0000	[thread overview]
Message-ID: <89D49ADA-A351-4CF8-98A9-81AD84C53E3A@etr-usa.com> (raw)
In-Reply-To: <1721a243f6fa4a32877cfdda157ad327@ntmaexbe04.bedford.progress.com>

On May 16, 2016, at 1:10 PM, Benjamin Cao <becao@progress.com> wrote:
> 
> I am curious to know if there is a command that will display a symbol table for *.obj files. It seems as if commands such as "nm" or "objdump" do not do this. I get "File format not recognized”.

nm *is* the right tool, but only for file types it knows about.

You should only expect a platform’s native nm to support the native executable types of the platform it runs on.  In the case of Cygwin, that’s various flavors of COFF and PE.  OMF is an entirely different format.

Cygwin’s nm happens to also support ELF for some reason, but that is yet a third object format.

Assuming libbfd knows OMF, you could rebuild your own OMF cross-development toolchain.  Then *its* nm would be the right tool for the job.

  https://en.wikipedia.org/wiki/Binary_File_Descriptor_library
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2016-05-16 19:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 19:11 Benjamin Cao
2016-05-16 19:35 ` Mark Geisert
2016-05-16 19:42 ` Warren Young [this message]
2016-05-16 20:05 ` Yaakov Selkowitz
2016-05-19 20:29   ` Hans-Bernhard Bröker

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=89D49ADA-A351-4CF8-98A9-81AD84C53E3A@etr-usa.com \
    --to=wyml@etr-usa.com \
    --cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).