<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: determine C objects in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/determine-c-objects/m-p/3075455#M718102</link>
    <description>if hp cc/aCC has been used, the following commands can help with unstripped binaries:&lt;BR /&gt;"odump -compunit" for 32-bit SOM binaries &amp;amp; "elfdump -dc" for 64-bit ELF binraies.</description>
    <pubDate>Mon, 22 Sep 2003 11:35:02 GMT</pubDate>
    <dc:creator>ranganath ramachandra</dc:creator>
    <dc:date>2003-09-22T11:35:02Z</dc:date>
    <item>
      <title>determine C objects</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/determine-c-objects/m-p/3075454#M718101</link>
      <description>hello all! I want to determine the C source files that I compiled an executable with.&lt;BR /&gt;example:&lt;BR /&gt; gcc -o example main1.c sub1.c sub2.c&lt;BR /&gt;&lt;BR /&gt;so I get an example exe.&lt;BR /&gt;&lt;BR /&gt;Problem:&lt;BR /&gt;Given only the executable and not knowing which files it was compiled with. Is it possible to determine the *.c files he/she used to compile the executable?&lt;BR /&gt;&lt;BR /&gt;any help is much appreciated. thanks! :)</description>
      <pubDate>Fri, 19 Sep 2003 19:24:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/determine-c-objects/m-p/3075454#M718101</guid>
      <dc:creator>mango_1</dc:creator>
      <dc:date>2003-09-19T19:24:43Z</dc:date>
    </item>
    <item>
      <title>Re: determine C objects</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/determine-c-objects/m-p/3075455#M718102</link>
      <description>if hp cc/aCC has been used, the following commands can help with unstripped binaries:&lt;BR /&gt;"odump -compunit" for 32-bit SOM binaries &amp;amp; "elfdump -dc" for 64-bit ELF binraies.</description>
      <pubDate>Mon, 22 Sep 2003 11:35:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/determine-c-objects/m-p/3075455#M718102</guid>
      <dc:creator>ranganath ramachandra</dc:creator>
      <dc:date>2003-09-22T11:35:02Z</dc:date>
    </item>
    <item>
      <title>Re: determine C objects</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/determine-c-objects/m-p/3075456#M718103</link>
      <description>It's possible if you are a little bit creative with the way you create your source files.&lt;BR /&gt;&lt;BR /&gt;Add the line:&lt;BR /&gt;&lt;BR /&gt;static char ident[]="@(#)foo.c";&lt;BR /&gt;&lt;BR /&gt;At the top of your source file.  That way, when you compile it into an object file, that string "@(#)foo.c" will be embedded within your object file, and the resulting executable.  Then you can use the "what" command to extract the information from your object.&lt;BR /&gt;&lt;BR /&gt;# cc -o foo foo1.c foo2.c&lt;BR /&gt;# what foo&lt;BR /&gt;foo:&lt;BR /&gt;    $Revision: 92453-07 linker linker crt0.o B.11.33 020617 $&lt;BR /&gt;    foo1.c&lt;BR /&gt;    foo2.c&lt;BR /&gt;&lt;BR /&gt;Hope this helps.</description>
      <pubDate>Tue, 20 Jan 2004 17:17:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/determine-c-objects/m-p/3075456#M718103</guid>
      <dc:creator>Kenneth Platz</dc:creator>
      <dc:date>2004-01-20T17:17:53Z</dc:date>
    </item>
  </channel>
</rss>

