Re: Problem debugging core dump in gdb 7.1 on Solaris x86_64

[Max Kaehn <slothman@electric-cloud.com>]

On 06/22/2010 04:18 PM, Michael Snyder wrote:
> 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.
>    
Certainly worth a try...  sadly, same result:

(gdb) set solib-search-path 
/lib:/usr/lib:/lib/amd64:/usr/lib/amd64:/net/tools/util/i686_SunOS_64.5.10/lib:/net/tools/util/i686_SunOS.5.10/lib/amd64
(gdb) core-file 
/net/chronic2nas/emake-slothman-main-201006211520/logs-201006211902-solx2-ea2/core
[New LWP 1]
[New LWP 2]
[New LWP 3]
[New LWP 4]
[New LWP 5]
Reading symbols from /usr/lib/amd64/ld.so.1...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/amd64/ld.so.1
Core was generated by `/opt/ecloud/i686_SunOS.5.10/bin/ecagent 
/opt/ecloud/i686_SunOS.5.10/bin/runagen'.
Program terminated with signal 11, Segmentation fault.
#0  0xfffffd7ffeac431c in ?? ()
(gdb) bt
#0  0xfffffd7ffeac431c in ?? ()
Cannot access memory at address 0xfffffd7fffdfed30
(gdb) info sharedlibrary
From                To                  Syms Read   Shared Object Library
0xfffffd7fff3c1010  0xfffffd7fff3e614e  Yes (*)     /usr/lib/amd64/ld.so.1
(*): Shared library is missing debugging information.

Thanks for the suggestion, though.