03-23-2007
I need to examine the stack trace inside the C program not to dump it to the shell.
10 More Discussions You Might Find Interesting
1. Programming
I am using gdb to examine a core file but the output contains only the method addresses in hex.
Is there anyway to translate these addresses to a human-readable form? :confused: (0 Replies)
Discussion started by: ciregbu
0 Replies
2. Programming
I am trying to print a stack trace programatically using backtrace and backtrace_symbols.
The problem is that the stack being printed in a mangled format. Is there a way to get the output in more of a human readable form?
I am using Red Hat and the program is written in c++. (2 Replies)
Discussion started by: dmirza
2 Replies
3. Shell Programming and Scripting
Hi all,
I was hoping someone can point me in the right direction. I'm trying to filter out errors from a web log- any lines with ERROR in it. I know I could simply use the grep command to do this. However, there are times when a stack trace follows the error line. I would like to capture these... (2 Replies)
Discussion started by: gswhoops
2 Replies
4. UNIX for Advanced & Expert Users
Hi all,
One of our programs written in Java, produced this logfile. This job runs 48 threads and only one thread failed with this error. The code is a blackbox(external product), so cant look at the source code. From what I can infer from the log, the job was trying to write the log messages into... (9 Replies)
Discussion started by: ranj@chn
9 Replies
5. Solaris
Hello ,
I use Solaris 5.10 . I have huge core file , 48 GB , resulted from an application that was running and got crashed with SIGSEGV.
On my system only mdb works. Please help me to retrieve the stack trace from this core file.
I am novice to mdb and its nuaunces. Please help me with... (2 Replies)
Discussion started by: rmv
2 Replies
6. AIX
Hi All,
I am trying to debug my core file using kdb.
When I try to get the stack trace I am facing this error.
core mapped from @ 700000000000000 to @ 70000000306fc04
Preserving 1680415 bytes of symbol table
Dump does not start with valid magic number
WARNING: Possibly truncated or... (2 Replies)
Discussion started by: Sachin1987
2 Replies
7. Shell Programming and Scripting
Hi All
Thought it would be kind of fun to implement a stack trace for a shell script that calls functions within a sub shell. This is for bash under Linux and probably not portable -
#! /bin/bash
error_exit()
{
echo "======================="
echo $1
echo... (4 Replies)
Discussion started by: steadyonabix
4 Replies
8. Programming
I have a C program which is running as daemon and has some threads.
The program is running on dual core cpu and it may happen that different threads may run on different cpu core.
The problem is sometimes it crashes with some heap memory corruption probably between threads.
GDB command(t a a... (2 Replies)
Discussion started by: rupeshkp728
2 Replies
9. Linux
Hi everyone,
Our Red Hat server hung yesterday, and I managed to log into the console and see the following message:
RIP: 0010: mwait_idle_with_hints+0x66/
0x67
RSP: 0018:ffffffff80457f40 EFLAGS: 00000046
RAX: 0000000000000010 RBX: ffff810c20075910 RCX: 0000000000000001
RDX:... (6 Replies)
Discussion started by: badoshi
6 Replies
10. Shell Programming and Scripting
I want the developers to get a mail with Java stack traces on a daily bases. When something is flaged as known issue and will get a fix but mean while this does not need to get sent each dayl. This is what I got so far. It's a bash script that runs some AWK in it.
To get the files that needs to... (6 Replies)
Discussion started by: chipmunken
6 Replies
trace(1) General Commands Manual trace(1)
Name
trace - trace system calls of programs
Syntax
trace [options] cmd args...
Description
The command with no flag arguments traces for the given cmd and args all system calls made and prints a time stamp, the PID, call and/or
return values and arguments and puts its output in the file trace.dump.
Options
-f filename
Puts dump in file filename.
-z Echos arguments only.
Only one of the following option arguments can be specified at one time.
-c# Traces given PIDs and their children. Up to sixteen PIDs can be specified.
-g# Traces given groups only. Up to sixteen Group IDs can be specified.
-p# Traces given PIDs only. Up to sixteen PIDs can be specified.
-s# Traces given system calls only. Up to sixteen PIDs can be specified.
-u# Traces given UIDs only. Up to sixteen PIDs can be specified.
Examples
trace -f ls.dump ls -l /dev >ls.out
runs the cmd ls -l /dev and puts the trace in ls.dump and output in ls.out.
trace -f csh.trace -p $$ &
will trace your login shell in the background. To stop the trace just send it a termination signal (that is, kill -TERM trace_pid).
Restrictions
Due to security, no one, not even the super-user can trace anyone else's programs. This sort of negates some of the usefulness of the -g
and -u flags.
The program cannot be traced.
Only 16 numbers can be given to the -c, -p, -g, -u, and -s flags.
The kernel configuration file must contain the following:
options SYS_TRACE
pseudo-device sys_trace
In addition, the superuser must use the following command sequence to create the device:
cd /dev
MAKEDEV trace
If both lines are not in the configuration file or if the device is not made, the message "Cannot open /dev/trace" appears.
Files
/dev/trace read only character special device for reading syscall data.
trace.dump default file for the system call trace data.
See Also
open(2), close(2), ioctl(2), select(2), read(2), trace(5)
trace(1)