strings embarqcsn01_sip* | grep '\$Id'


what sipconn | grep '\$Id'
what embarqcsn01_sip* | grep '\$Id'
what embarqcsn01_sip* | grep RadvisionStackUtil
what libSnsSipStack.so | grep '\$Id' |grep Radvision //gives ID's and version

cd ../lib
nm * | grep -i isTelUri
nm /home/csn_test/lib/libSnsSipStack.so |grep isTelUri  //gives function in library


ldd bin/sipconn | more
ldd ../bin/sipconn //against what libraries was linked


cat data/sns.readme
cd data
ls
cat version



rm -fr bin lib data db dumps idl src var
pwd
ls
gunzip *.gz

tar tf CSN-R3_2_1-143.tar | more
tar tf *patch2.tar | more

tar xf CSN-R3_2_1-143.tar
tar xf R3_2_1-143_patch2.tar
proc -map | more


help core mismatch

==================================
in DBX:== Here is an explanation of the problem:

Sometimes a core file is created on one system (the core-host) and
you want to load the core file on another machine (the dbx-host).  One
problem is the shared libraries used by the program on the core-host
won't be the same libraries as those on the dbx-host.

To get proper stack traces involving the libraries, you'll want to make these original
libraries available on the dbx-host and use the options explained
below to tell dbx where to look for those libraries.


Another problemis that dbx uses system libraries in /usr/lib to help understand the
implementation details of the run time linker and threads library
on the system.  It may also be necessary to provide these system
libraries from the core-host so that dbx can understand the
runtime linker data structures and the threads data structures.

//The user libraries and system libraries can change in patches
//as well as major Solaris upgrades, so this problem can even
//show up (for example) on the same host, if a patch was installed
//after the core file was collected, but before running dbx on the
//core file.

Here are some of the errors that might show up if you are looking at a
mismatched core file.  Usually, only one or two of these will
show up at a time.


== Here is how to use dbx on a mismatched core file:

1. turn on the `core_lo_pathmap' dbxenv variable.
2. use the pathmap command to tell dbx where the libraries are
3. use the debug command to load the program and the core file

The following example assumes that the root partition of the core-host
has been exported over NFS and can be accessed via /net/core-host/
on the dbx-host machine.

(dbx) dbxenv core_lo_pathmap on
(dbx) pathmap /usr      /net/core-host/usr
(dbx) pathmap /appstuff /net/core-host/appstuff
(dbx) debug prog prog.core

In the case where you aren't exporting the root partition of
the core-host, you will need to copy the libraries by hand.
It's not necessary to re-create the symbolic links. (For example,
you don't need to make a link from libc.so -> libc.so.1, just
make sure libc.so.1 is available.)

Things to remember:

 - The pathmap command doesn't recognize a pathmap for '/' so you
   can't currently say: "pathmap / /net/core-host"

 - The single-argument mode for pathmap doesn't work with loadobject
   pathnames, so use the two argument <from-path to-path> mode.

 - It is likely that things will work best if the dbx-host
   has a either the same or a more recent version of Solaris than the
   core-host.  Although this is not always necessary.

 - The system libraries that might be needed are:
   For the runtime linker:
       /usr/lib/ld.so.1
       /usr/lib/librtld_db.so.1
       /usr/lib/sparcv9/ld.so.1
       /usr/lib/sparcv9/librtld_db.so.1
   For the threads library:
       /usr/lib/libthread_db.so.1
       /usr/lib/sparcv9/libthread_db.so.1
       /usr/lib/lwp/libthread_db.so.1
       /usr/lib/lwp/sparcv9/libthread_db.so.1
   Depending on which implementation of libthread you're using.


   ==========================================================================


(dbx) proc -map |more
Loadobject mappings for current core file:
0x00010000 /home/csn/bin/sipconn
0xff360000 /lib/libsocket.so.1
0xff280000 /lib/libnsl.so.1
0xff260000 /lib/librt.so.1
0xff240000 /home/csn/lib/libSnsConnector.so
  Warning: checksum in file(8bf8) doesn't match image(7ad5)
0xff180000 /home/csn/lib/libSnsNetworkCall.so
  Warning: checksum in file(210c) doesn't match image(b2f7)
0xff080000 /home/csn/lib/libSnsSipStack.so
  Warning: checksum in file(87a5) doesn't match image(eaf0)
0xff220000 /home/csn/lib/libSnsEvent.so
  Warning: checksum in file(bd3c) doesn't match image(9e6a)
0xff030000 /home/csn/lib/libSnsSicc.so
  Warning: checksum in file(07d1) doesn't match image(cb5e)
0xff150000 /home/csn/lib/libSnsUtils.so
  Warning: checksum in file(474f) doesn't match image(3642)
0xff000000 /home/csn/lib/libSnsSipPresence.so
  Warning: checksum in file(7bc1) doesn't match image(82c0)
0xfefd0000 /home/csn/lib/libSnsStatistics.so
  Warning: checksum in file(3d6b) doesn't match image(c109)
0xff398000 /lib/libpthread.so.1
           is being filtered by: libc.so.1
0xfefa0000 /home/csn/lib/libLogs.so
  Warning: checksum in file(a3aa) doesn't match image(9fd4)
0xfef20000 /home/csn/lib/libTimer.so
  Warning: checksum in file(f93c) doesn't match image(0697)
0xfed80000 /home/csn/lib/libeICC.so
  Warning: checksum in file(6452) doesn't match image(59fc)
0xfed10000 /home/csn/lib/libOam.so
  Warning: checksum in file(edb5) doesn't match image(e19d)
0xfec00000 /home/csn/lib/libCore++.so
  Warning: checksum in file(71f6) doesn't match image(bb52)
0xfecf0000 /home/csn/lib/libAlarm.so
  Warning: checksum in file(3fe1) doesn't match image(5446)
0xfeba0000 /lib/libresolv.so.2
0xfdc00000 /u01/app/oracle/product/10.2.0/lib32/libclntsh.so.10.1  (not loaded)
0xfecc0000 /home/csn/lib/libRdnPool.so




