<?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: shared executable dynamically linked in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/shared-executable-dynamically-linked/m-p/2525138#M878689</link>
    <description>Hi Jasmin:&lt;BR /&gt;&lt;BR /&gt;A good white-paper that addresses some of your questions is the "HP-UX 10.0 Memory Management White Paper", document #OMJWP02950928 in the Technical Knowledge Base.&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
    <pubDate>Fri, 04 May 2001 19:26:04 GMT</pubDate>
    <dc:creator>James R. Ferguson</dc:creator>
    <dc:date>2001-05-04T19:26:04Z</dc:date>
    <item>
      <title>shared executable dynamically linked</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shared-executable-dynamically-linked/m-p/2525136#M878687</link>
      <description>Can someone tell me what "shared executable dynamically linked" means, is that a C program, perl, I don't know.... Is there a way to decode those executables, just to understand what they do?</description>
      <pubDate>Fri, 04 May 2001 18:59:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shared-executable-dynamically-linked/m-p/2525136#M878687</guid>
      <dc:creator>Jasmin Berube</dc:creator>
      <dc:date>2001-05-04T18:59:53Z</dc:date>
    </item>
    <item>
      <title>Re: shared executable dynamically linked</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shared-executable-dynamically-linked/m-p/2525137#M878688</link>
      <description>Hi Jasmin:&lt;BR /&gt;&lt;BR /&gt;You asked for it so here goes:&lt;BR /&gt;&lt;BR /&gt;Shared Executable Dynamically Linked &lt;BR /&gt;Shared - more than one process can use the&lt;BR /&gt;'text' (the instructions as opposed to data)&lt;BR /&gt;segment simultaneously. (This saves system wide memory)&lt;BR /&gt;Executable - Directly executable code as opposed to a perl,shell,etc script which is interpreted.&lt;BR /&gt;Dynamically Linked - it's made ready for execution on a local machine 'on the fly'. Your particular machines shared libraries are used as opposed to statically linked where everything needed to run the code in linked on the machine on which is way created.&lt;BR /&gt;&lt;BR /&gt;The last part of your question is more difficult. The correct answer is possibly. If the programmer included debugger info then yes its possible to get some idea but very difficult.&lt;BR /&gt;&lt;BR /&gt;Unless this is a custom program, if you tell us the name of the execuatable, I'll bet someone on the forum will recogize it.&lt;BR /&gt;&lt;BR /&gt;Hope this clears up a few things, Clay.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 04 May 2001 19:09:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shared-executable-dynamically-linked/m-p/2525137#M878688</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-05-04T19:09:59Z</dc:date>
    </item>
    <item>
      <title>Re: shared executable dynamically linked</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shared-executable-dynamically-linked/m-p/2525138#M878689</link>
      <description>Hi Jasmin:&lt;BR /&gt;&lt;BR /&gt;A good white-paper that addresses some of your questions is the "HP-UX 10.0 Memory Management White Paper", document #OMJWP02950928 in the Technical Knowledge Base.&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Fri, 04 May 2001 19:26:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shared-executable-dynamically-linked/m-p/2525138#M878689</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-05-04T19:26:04Z</dc:date>
    </item>
  </channel>
</rss>

