Sponsored Content
Top Forums Programming Core File Not Being Generated in AIX Post 40514 by davidg on Wednesday 17th of September 2003 09:28:03 AM
Old 09-17-2003
Hi,

You could truss or tusc the process when you start the program.
In Solaris/HP-ux it goes like :

truss /program/to/start/myprog

When debugging an already running program you can do :

truss -p <processid>


There is one note :

AIX 5.1 has 'truss'.

AIX 4.3.3 and earlier you can use the 'trace' command - but it's a pain because it's a system-level trace from which you can then extract the information for the process you cared about.


Regs David
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

AIX - Core dump when using mkuser

Hi all, I've got a strange problem here that is not documented in AIX FAQs and tech docs, and I was wondering if somebody out there encountered the same issue or had an idea to help me out. I'm using a script to create users with the "mkuser" command. I can set up any options I want (like... (1 Reply)
Discussion started by: dfrangidis
1 Replies

2. AIX

Why a core file is created whenever I send a mail in AIX

Whenever i send a mail like: mail <mail id>, a core file is created under /var/spool/mqueue/ path. This is increasing the space of the file system. Why is that core file get created. Does it happens normally. I am getting an errpt error as: LABEL: CORE_DUMP IDENTIFIER: B6048838 ... (0 Replies)
Discussion started by: sreereddy
0 Replies

3. AIX

How to do core dump analysis in AIX?

Please tell me some methods to analyse core dump in AIX.:) (2 Replies)
Discussion started by: Mythili
2 Replies

4. Programming

AIX core dumps

My program is not dumping core when hitting a segmentation violation inside a thread. However, it dumps core when the segv occurs within main. Any ideas on how to diagnose this? AIX 5.3 (4 Replies)
Discussion started by: bean66
4 Replies

5. AIX

no of core in cpu for aix

is there command which will display no of core per cpu in aix? Regads, Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies

6. Solaris

core files not getting generated

Hi, We have an application ASPA . The application related processes are running in /ASPA/bin directory . now whenever a process terminates abruptly , a core file should be generated (correct me if i am wrong) in the /ASPA/bin directory . But i am not able to see any such files . The... (4 Replies)
Discussion started by: asalman.qazi
4 Replies

7. Linux

Core file not getting generated!!

Some strange behavior. Process is receiving Segmentation Fault. But no core files getting generated. I have checked ulimit. coredumpsize = unlimited. In console, process is printing Segmentation Fault even through gdb also same behavior But No corefile. Any possible reason ? ... (3 Replies)
Discussion started by: ashokd001
3 Replies

8. AIX

AIX core,cpu and application list

Hi All , I am trying to pull out below things from AIX machine (any type) 1. number of physical processor 2. number of logical processsors 3. Total number of processors (physical plus logical) 4. total number of cores 5. list of installed applications with versions and vendor name ... (1 Reply)
Discussion started by: omkar.jadhav
1 Replies

9. Programming

How to know which binary generated obtained core dump?

Hello, Suppose there are large number of binaries are executing on a system. Meanwhile, we find a dump, now how can we know from core dump that which binary file it is related to? Thanks ---------- Post updated at 02:01 PM ---------- Previous update was at 01:53 PM ---------- I have got... (1 Reply)
Discussion started by: ezee
1 Replies

10. AIX

Adding CR to ascii data file generated on AIX platform and will be transmitted to Windows OS

I desperately need help converting ascii data file generated on AIX platform that contains dollar sign ($) at the end of each line in the data file as shown below. ME570^0128237^HG278999^20140805:21:00:00^BEENZ001^$ This is the AWK command for adding CR to the new line. awk... (1 Reply)
Discussion started by: cumeh1624
1 Replies
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.11 12 May 1997 sotruss(1)
All times are GMT -4. The time now is 10:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy