<?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 ldd like tool for in-memory process in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-like-tool-for-in-memory-process/m-p/4907785#M838461</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Is there a tool like "ldd" which can accept the PID of a process in execution, and display the pathnames of the various libraries loaded dynamically and linked-to ? I'm just hoping against the odds...&lt;BR /&gt;&lt;BR /&gt;cheers,&lt;BR /&gt;bd</description>
    <pubDate>Fri, 17 Jun 2005 02:43:06 GMT</pubDate>
    <dc:creator>Banibrata Dutta</dc:creator>
    <dc:date>2005-06-17T02:43:06Z</dc:date>
    <item>
      <title>ldd like tool for in-memory process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-like-tool-for-in-memory-process/m-p/4907785#M838461</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Is there a tool like "ldd" which can accept the PID of a process in execution, and display the pathnames of the various libraries loaded dynamically and linked-to ? I'm just hoping against the odds...&lt;BR /&gt;&lt;BR /&gt;cheers,&lt;BR /&gt;bd</description>
      <pubDate>Fri, 17 Jun 2005 02:43:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ldd-like-tool-for-in-memory-process/m-p/4907785#M838461</guid>
      <dc:creator>Banibrata Dutta</dc:creator>
      <dc:date>2005-06-17T02:43:06Z</dc:date>
    </item>
    <item>
      <title>Re: ldd like tool for in-memory process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-like-tool-for-in-memory-process/m-p/4907786#M838462</link>
      <description>I suggest use lsof command.&lt;BR /&gt;&lt;BR /&gt;# lsof -p 11086 | awk '$4=="mem"'&lt;BR /&gt;telnetd 11086 root  mem    REG     64,0x7    36864 10488 /usr/lib/libnss_dns.1&lt;BR /&gt;telnetd 11086 root  mem    REG     64,0x7    53248 29984 /usr/lib/libnss_files.1&lt;BR /&gt;telnetd 11086 root  mem    REG     64,0x7   135168   116 /usr/lib/libxti.2&lt;BR /&gt;telnetd 11086 root  mem    REG     64,0x7   741376 30172 /usr/lib/libnsl.1&lt;BR /&gt;telnetd 11086 root  mem    REG     64,0x7    45056 30173 /usr/lib/libnss_nis.1&lt;BR /&gt;telnetd 11086 root  mem    REG     64,0x7  1044480   118 /usr (/dev/vg00/lvol7)&lt;BR /&gt;telnetd 11086 root  mem    REG     64,0x7    24576 29836 /usr/lib/libdld.2&lt;BR /&gt;telnetd 11086 root  mem    REG     64,0x7  1814528 27903 /usr/lib/libc.2&lt;BR /&gt;telnetd 11086 root  mem    REG     64,0x7   241664 28460 /usr/lib/dld.sl&lt;BR /&gt;telnetd 11086 root  mem    REG     64,0x8      532  2449 /var/spool/pwgr/status</description>
      <pubDate>Fri, 17 Jun 2005 03:00:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ldd-like-tool-for-in-memory-process/m-p/4907786#M838462</guid>
      <dc:creator>CAS_2</dc:creator>
      <dc:date>2005-06-17T03:00:42Z</dc:date>
    </item>
    <item>
      <title>Re: ldd like tool for in-memory process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-like-tool-for-in-memory-process/m-p/4907787#M838463</link>
      <description>Thanks CAS, but "lsof" is something I've already tried and found that due to the "snapshot" nature of info. it provides, you cannot really tell what all ".sl"'s it is linked against and what all ".sl"'s have been demand-loaded (dynamically, using dlopen() for instance). &lt;BR /&gt;&lt;BR /&gt;I believe that when demand load is done, dld.so opens the file, reads it, loads the text segments into memory after relocation, update the link tables, and finally close the file... (just a hunch). Because I am not seeing so monay .sl files (via "lsof), that ldd -v shows, and I know that they are loaded because I am able to use the functionality delivered by those shared libs!!&lt;BR /&gt;&lt;BR /&gt;thanks for the info anyway.&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;bd</description>
      <pubDate>Fri, 17 Jun 2005 03:18:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ldd-like-tool-for-in-memory-process/m-p/4907787#M838463</guid>
      <dc:creator>Banibrata Dutta</dc:creator>
      <dc:date>2005-06-17T03:18:31Z</dc:date>
    </item>
    <item>
      <title>Re: ldd like tool for in-memory process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-like-tool-for-in-memory-process/m-p/4907788#M838464</link>
      <description>Well, i found the way, albeit quite crude.&lt;BR /&gt;I knew which all .sl's I was suspecting to be used, but couldn't get "ldd" to report them (since they were loaded on demand). I simply started the process in question, and did an "fuser" on the suspected .sl file, and that's it. It confirmed it's use.&lt;BR /&gt;&lt;BR /&gt;thanks,&lt;BR /&gt;bdutta</description>
      <pubDate>Fri, 17 Jun 2005 10:23:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ldd-like-tool-for-in-memory-process/m-p/4907788#M838464</guid>
      <dc:creator>Banibrata Dutta</dc:creator>
      <dc:date>2005-06-17T10:23:35Z</dc:date>
    </item>
    <item>
      <title>Re: ldd like tool for in-memory process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-like-tool-for-in-memory-process/m-p/4907789#M838465</link>
      <description>see my last post.</description>
      <pubDate>Fri, 17 Jun 2005 10:24:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ldd-like-tool-for-in-memory-process/m-p/4907789#M838465</guid>
      <dc:creator>Banibrata Dutta</dc:creator>
      <dc:date>2005-06-17T10:24:14Z</dc:date>
    </item>
  </channel>
</rss>

