Hello,
I'm new to the group and this is my first post. I'm hoping someone can help me out. I have a core dump that I need to analyze from a Unix box and I've never done this sort of thing before. I was told to run a pmap and pstack on the core file which provided two different output files. ... (3 Replies)
Hi,
Can we modify the GDB source code so as to analyze core dumps from different targets? From my analysis, I think we need to build our section table statically for each target. i.e., including the various address boundaries in build_section_table() function. If this is the case, then the GDB... (2 Replies)
Hi all,
I need a script that will loop around all the current processes and take a pmap -x <process id> and output each pmap to a separate file.
Would anyone have a quick command to do this? (2 Replies)
Dear All,
I am new to this forum. This is my first.
I am facing customer issue. Customer has got core file while running the server.
He had sent core file and details from pstack, pmap and pldd commands.
I have to debug this application, please help me to fix this issue.
I am using sparc... (1 Reply)
Hi,
I have some question about memory in Solaris.
How it's possible that prstat -a show me that some process using 230M RSS and when I'm using pmap -x show me that this same process using only 90M RSS ? (0 Replies)
I would to create a command /script where I want lauch pmap -x pid for each procces which is launched on server , and I don't know how to write a loop where it would be included . (2 Replies)
Hi,
Someone please analyse the following o/p of fdisk -l and tell me what it means for /dev/sda, /dev/sdb, /dev/sdc ....
Disk /dev/sda: 53.6 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start ... (5 Replies)
Hi All,
When can we see these messages in the syslog.
We have service guard cluster software installed on hpux 11iv3 servers.
We were able to see the below error so many times in our syslog messages
cmdisklockd: Unable to convert device to I/O tree node: I/O tree node does not exist.
... (2 Replies)
Discussion started by: Sachin1987
2 Replies
LEARN ABOUT SUNOS
sotruss
sotruss(1) User Commands sotruss(1)NAME
sotruss - trace shared library procedure calls
SYNOPSIS
/usr/bin/sotruss [-f] [-F bindfromlist] [-T bindtolist] [-o outputfile] executable [ executable arguments...]
DESCRIPTION
sotruss executes the specified command and produces a trace of the library calls that it performs. Each line of the trace output reports
what bindings are occurring between dynamic objects as each procedure call is executed. sotruss traces all of the procedure calls that
occur between dynamic objects via the Procedure Linkage Table, so only those procedure calls which are bound via the Procedure Linkage Ta-
ble will be traced. See Linker and Libraries Guide
OPTIONS -F bindfromlist A colon-separated list of libraries that are to be traced.
Only calls from these libraries will be traced. The default is to trace calls from the main executable only.
-T bindtolist A colon-separated list of libraries that are to be traced. Only calls to these libraries will be traced.
The default is to trace all calls.
-o outputfile sotruss output will be directed to the outputfile. If this option is combined with the -f option then the pid of
the executing program will be placed at the end of the filename. By default sotruss output is placed on stderr.
-f Follow all children created by fork() and print truss output on each child process. This option will also cause
a pid to be output on each truss output line.
EXAMPLES
Example 1: An example of sotruss.
A simple example shows the tracing of a simple ls command:
% sotruss ls | more
ls -> libc.so.1:*atexit(0xef7d7d1c, 0x23c00, 0x0)
ls -> libc.so.1:*atexit(0x1392c, 0xef7d7d1c, 0xef621bb0)
ls -> libc.so.1:*setlocale(0x6, 0x1396c, 0xef621ba8)
ls -> libc.so.1:*textdomain(0x13970, 0x1396c, 0xef621ba8)
ls -> libc.so.1:*time(0x0, 0xef61f6fc, 0xef621ba8)
ls -> libc.so.1:*isatty(0x1, 0xef61f6fc, 0x0)
ls -> libc.so.1:*getopt(0x1, 0xeffff8fc, 0x13980)
ls -> libc.so.1:*malloc(0x100, 0x0, 0x0)
ls -> libc.so.1:*malloc(0x9000, 0x0, 0x0)
ls -> libc.so.1:*lstat64(0x23ee8, 0xeffff7a0, 0x0)
...
ls -> libc.so.1:*printf(0x13a64, 0x26208, 0x23ef0)
ls -> libc.so.1:*printf(0x13a64, 0x26448, 0x23ef0)
ls -> libc.so.1:*exit(0x0, 0x24220, 0x2421c)
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWtoo |
+-----------------------------+-----------------------------+
SEE ALSO ld.so.1(1), truss(1), whocalls(1), fork(2), attributes(5)
Linker and Libraries Guide
SunOS 5.10 12 May 1997 sotruss(1)