analyse core file using pmap and pstack Post: 302429282

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Core Dump Analysis Using PStack and PMAP

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. ...

2. UNIX for Advanced & Expert Users

Using GDB to analyse different CORE dumps

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...

3. Shell Programming and Scripting

script to loop all process ids and take pmap

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?

4. Red Hat

pmap -d ldap-process-id

Hi All, Is the command above dangerous to run on the ldap environment? Thanks for any comments you may add.

5. UNIX for Advanced & Expert Users

analyse core file using pmap and pstack

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...

6. Solaris

RSS pmap and prstat

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 ?

7. Solaris

loop for pmap -x

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 .

8. Solaris

pstack file analysis

Hi ... Can you please share how to analyse pstack file and various options for core dump analysis

9. UNIX for Dummies Questions & Answers

Analyse this fdisk -l

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 ...

10. HP-UX

How to analyse the syslog?

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. ...

LEARN ABOUT DEBIAN

sdcdb

SDCDB(1)						      General Commands Manual							  SDCDB(1)

NAME

       sdcdb - Source debugger for SDCC

SYNOPSIS

       sdcdb [options] filename

WARNING

       The information in this man page is an extract from the full documentation of SDCC, and is limited to the meaning of the options.

       For complete and current documentation, refer to the SDCC Compiler User Guide.

DESCRIPTION

       sdcdb is a source debugger for SDCC. It uses ucSim to execute the program, the programm execution is controlled by the debugger.

       The  command  interface for the debugger has been deliberately kept as close the GNU debugger gdb, as possible. This will help the integra-
       tion with existing graphical user interfaces (like ddd, xxgdb or xemacs) existing for the GNU debugger.

STARTING THE DEBUGGER

       The debugger can be started using the following command line (Assume the file you are debugging has the file name foo):

       sdcdb foo

       The debugger will look for the following files:

       foo.c   - the source file.
       foo.cdb - the debugger symbol information file.
       foo.ihx - the intel hex format object file.

OPTIONS

       -directory=<source file directory>
	      This option can used to specify the directory search list. The debugger will look into the directory list specified for source,  cdb
	      & ihx files. The items in the directory list must be separated by ':', e.g. if the source files can be in the directories /home/src1
	      and /home/src2, the -directory option should be -directory=/home/src1:/home/src2. Note there can be no spaces in the option.

       -cd <directory>
	      Change to the <directory>.

       -fullname
	      Used by GUI front ends.

       -cpu <cpu-type>
	      This argument is passed to the simulator. Please see the simulator docs for details.

       -X <Clock frequency>
	      This option is passed to the simulator. Please see the simulator docs for details.

       -s <serial port file>
	      This option is passed to simulator. Please see the simulator docs for details.

       -S <serial in,out>
	      This argument is passed to simulator. Please  see the simulator docs for details.

COPYING

       The entire source code for the debugger is distributed under GNU General Public License.

SEE ALSO

       sdcc(1), ucsim(1), s51(1), savr(1), sz80(1).

AUTHOR

       This manual page was written by Aurelien Jarno <aurel32@debian.org>, for the Debian GNU/Linux system (but may be used by others).

																	  SDCDB(1)

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Core Dump Analysis Using PStack and PMAP

Discussion started by: kimblebee

2. UNIX for Advanced & Expert Users

Using GDB to analyse different CORE dumps

Discussion started by: nsdeeps

3. Shell Programming and Scripting

script to loop all process ids and take pmap

Discussion started by: borderblaster

4. Red Hat

pmap -d ldap-process-id

Discussion started by: itik