From: Michael Snyder <msnyder@vmware.com>
To: Max Kaehn <slothman@electric-cloud.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Problem debugging core dump in gdb 7.1 on Solaris x86_64
Date: Tue, 22 Jun 2010 23:18:00 -0000 [thread overview]
Message-ID: <4C2144BD.1030100@vmware.com> (raw)
In-Reply-To: <4C214057.8060806@electric-cloud.com>
Max Kaehn wrote:
> On 06/22/2010 12:21 PM, Michael Snyder wrote:
>> Seems like the only shared library that got loaded was ld.so.
>>
>> Should more shared libs (eg. libc) be loaded?
>>
>> Could there be an issue with finding the needed shared libs?
>>
> "ldd" seems to be able to find them; I would hope gdb would be able to
> use the same mechanisms.
Hmmm, well I don't know if those are the standard locations, but
you might try using "set solib-search-path" before loading the
corefile.
>
> solx2-ea2% ldd
> /net/chronic2nas/emake-slothman-main/out/i686_SunOS_64.5.10/ecloud/agent/ecagent
> libcurl.so.4 =>
> /net/tools/util/i686_SunOS_64.5.10/lib/libcurl.so.4
> libssl.so.0.9.8 =>
> /net/tools/util/i686_SunOS_64.5.10/lib/libssl.so.0.9.8
> libcrypto.so.0.9.8 =>
> /net/tools/util/i686_SunOS_64.5.10/lib/libcrypto.so.0.9.8
> libpthread.so.1 => /lib/amd64/libpthread.so.1
> libtcl8.6.so =>
> /net/tools/util/i686_SunOS_64.5.10/lib/libtcl8.6.so
> libz.so.1 => /net/tools/util/i686_SunOS_64.5.10/lib/libz.so.1
> libsocket.so.1 => /lib/amd64/libsocket.so.1
> libnsl.so.1 => /lib/amd64/libnsl.so.1
> librt.so.1 => /lib/amd64/librt.so.1
> libiconv.so.2 =>
> /net/tools/util/i686_SunOS_64.5.10/lib/libiconv.so.2
> libstdc++.so.6 =>
> /net/tools/util/i686_SunOS.5.10/lib/amd64/libstdc++.so.6
> libm.so.2 => /lib/amd64/libm.so.2
> libgcc_s.so.1 =>
> /net/tools/util/i686_SunOS.5.10/lib/amd64/libgcc_s.so.1
> libc.so.1 => /lib/amd64/libc.so.1
> libldap.so.5 => /usr/lib/amd64/libldap.so.5
> libdl.so.1 => /lib/amd64/libdl.so.1
> libz.so.1 (SUNW_1.1) => (version not found)
> libz.so.1 (SUNW_1.2) => (version not found)
> libmp.so.2 => /lib/amd64/libmp.so.2
> libmd.so.1 => /lib/amd64/libmd.so.1
> libscf.so.1 => /lib/amd64/libscf.so.1
> libaio.so.1 => /lib/amd64/libaio.so.1
> libsasl.so.1 => /usr/lib/amd64/libsasl.so.1
> libnspr4.so => /usr/lib/mps/64/libnspr4.so
> libplc4.so => /usr/lib/mps/64/libplc4.so
> libnss3.so => /usr/lib/mps/64/libnss3.so
> libssl3.so => /usr/lib/mps/64/libssl3.so
> libdoor.so.1 => /lib/amd64/libdoor.so.1
> libuutil.so.1 => /lib/amd64/libuutil.so.1
> libgen.so.1 => /lib/amd64/libgen.so.1
> libnssutil3.so => /usr/lib/mps/amd64/libnssutil3.so
> libplds4.so => /usr/lib/mps/amd64/libplds4.so
> libthread.so.1 => /lib/amd64/libthread.so.1
>
next prev parent reply other threads:[~2010-06-22 23:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 19:06 Max Kaehn
2010-06-22 19:21 ` Michael Snyder
2010-06-22 22:59 ` Max Kaehn
2010-06-22 23:18 ` Michael Snyder [this message]
2010-06-22 23:56 ` Max Kaehn
2010-06-22 22:16 ` Max Kaehn
2010-06-25 17:03 ` Max Kaehn
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=4C2144BD.1030100@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=slothman@electric-cloud.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