<?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 Tell adb to load libs from alt dirs in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/tell-adb-to-load-libs-from-alt-dirs/m-p/4761750#M657142</link>
    <description>I have a core file generated on an HP IA64 machine. I have the executable and shared objects related to the core file. I am trying to get the call stack using the adb debugger but the core file was generated on a machine I don't have access to, so the shared objects are in a different location than they are at the time the core file was generated.&lt;BR /&gt;&lt;BR /&gt;I know if I have a similar situation using gdb I would do the following:&lt;BR /&gt;&lt;BR /&gt;machine:user&amp;gt; gdb&lt;BR /&gt;(gdb) set solib-search-path path1:path2:path3&lt;BR /&gt;(gdb) file &lt;NAME of="" executable="" file=""&gt;&lt;BR /&gt;(gdb) core &lt;NAME of="" core="" file=""&gt;&lt;BR /&gt;Where the setting of solib-search-path tells gdb where to load shared libraries from.&lt;BR /&gt;&lt;BR /&gt;Is there an equivalent if I'm using adb?&lt;/NAME&gt;&lt;/NAME&gt;</description>
    <pubDate>Fri, 04 Mar 2011 20:22:20 GMT</pubDate>
    <dc:creator>Reuben Cox</dc:creator>
    <dc:date>2011-03-04T20:22:20Z</dc:date>
    <item>
      <title>Tell adb to load libs from alt dirs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tell-adb-to-load-libs-from-alt-dirs/m-p/4761750#M657142</link>
      <description>I have a core file generated on an HP IA64 machine. I have the executable and shared objects related to the core file. I am trying to get the call stack using the adb debugger but the core file was generated on a machine I don't have access to, so the shared objects are in a different location than they are at the time the core file was generated.&lt;BR /&gt;&lt;BR /&gt;I know if I have a similar situation using gdb I would do the following:&lt;BR /&gt;&lt;BR /&gt;machine:user&amp;gt; gdb&lt;BR /&gt;(gdb) set solib-search-path path1:path2:path3&lt;BR /&gt;(gdb) file &lt;NAME of="" executable="" file=""&gt;&lt;BR /&gt;(gdb) core &lt;NAME of="" core="" file=""&gt;&lt;BR /&gt;Where the setting of solib-search-path tells gdb where to load shared libraries from.&lt;BR /&gt;&lt;BR /&gt;Is there an equivalent if I'm using adb?&lt;/NAME&gt;&lt;/NAME&gt;</description>
      <pubDate>Fri, 04 Mar 2011 20:22:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tell-adb-to-load-libs-from-alt-dirs/m-p/4761750#M657142</guid>
      <dc:creator>Reuben Cox</dc:creator>
      <dc:date>2011-03-04T20:22:20Z</dc:date>
    </item>
    <item>
      <title>Re: Tell adb to load libs from alt dirs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tell-adb-to-load-libs-from-alt-dirs/m-p/4761751#M657143</link>
      <description>&amp;gt;I am trying to get the call stack using the adb debugger&lt;BR /&gt;&lt;BR /&gt;Don't even think of using adb, use gdb.  Just download the latest.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;but the core file was generated on a machine I don't have access to&lt;BR /&gt;&lt;BR /&gt;This is where gdb's packcore will help.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;using gdb I would do the following:&lt;BR /&gt;(gdb) set solib-search-path path1:path2:path3&lt;BR /&gt;&lt;BR /&gt;That seems too hard.  unpackcore or exporting GDB_SHLIB_PATH will be easier.</description>
      <pubDate>Sat, 05 Mar 2011 01:48:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tell-adb-to-load-libs-from-alt-dirs/m-p/4761751#M657143</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2011-03-05T01:48:21Z</dc:date>
    </item>
  </channel>
</rss>

