This is a basic one. Adding gdb or dbx to it requires taking the find output and the $PATH expected or extracted from the core to find the executable. One nice trick with a core file is to run it through 'strings' or 'cat -v' and look for the environment, usually near the end and in ASCII: PATH=.... Using gdb for where (stack trace) solved licensing issues (dbx only ran on dev boxes).
Hi folks,
I'm hoping someone would be charitable enough to give me a quick explanation of adb usage for analyzing core files...or point me in the right direction. A search here revealed scant results and web searches are providing me with ambiguous information.
Running Solaris.
Thanks,... (1 Reply)
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)
Hello everyone,
I have a 12-thread application running on Solaris 9.
When I use the pstack command after a typical core dump, it prints the stack output of all 12 threads/lwps. This is the standard procedure as it is described in the Solaris MAN pages.
Is there a way to filter out the... (1 Reply)
Hello,
I have a text file containin 4 lines which are repeated along the file, ie
the file looks like this:
16:20:12.060769 blablabla 40
16:20:12.093199 blablabla 640
16:20:12.209003 blablabla 640
16:20:12.273179 blablabla 216
16:20:27.217444 blablabla 40
16:20:27.235410 blablabla 640... (2 Replies)
How can we analyze a core file and determine why it was generated on a solaris system?
I know file core filename will tell us what program generated the file. But, what to do next to get more details?
Thanks, (5 Replies)
Hi All,
Given a list of date and time, how can i split them in intervals of 1 hour. The input file is listed as below f.e.:
16-OCT-2009 09:11:47 10.65.4.24.
.
. (1 Reply)
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)
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 10... (4 Replies)
Hi All
I would like to use the tool "pstack" to get a sample of the stack trace for a process.
As far as I understood It seems widely available in all Linux systems, but it is not in Ubuntu 10.10.
I tried using apt-get as per some posts in few forum, but it cannot be found in the APT... (9 Replies)
Discussion started by: manustone
9 Replies
LEARN ABOUT SUNOS
echo
echo(1B) SunOS/BSD Compatibility Package Commands echo(1B)NAME
echo - echo arguments to standard output
SYNOPSIS
/usr/ucb/echo [-n] [argument]
DESCRIPTION
echo writes its arguments, separated by BLANKs and terminated by a NEWLINE, to the standard output.
echo is useful for producing diagnostics in command files and for sending known data into a pipe, and for displaying the contents of envi-
ronment variables.
For example, you can use echo to determine how many subdirectories below the root directory (/) is your current directory, as follows:
o echo your current-working-directory's full pathname
o pipe the output through tr to translate the path's embedded slash-characters into space-characters
o pipe that output through wc -w for a count of the names in your path.
example% /usr/bin/echo "echo $PWD | tr '/' ' ' | wc -w"
See tr(1) and wc(1) for their functionality.
The shells csh(1), ksh(1), and sh(1), each have an echo built-in command, which, by default, will have precedence, and will be invoked if
the user calls echo without a full pathname. /usr/ucb/echo and csh's echo() have an -n option, but do not understand back-slashed escape
characters. sh's echo(), ksh's echo(), and /usr/bin/echo, on the other hand, understand the black-slashed escape characters, and ksh's
echo() also understands a as the audible bell character; however, these commands do not have an -n option.
OPTIONS -n Do not add the NEWLINE to the output.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscpu |
+-----------------------------+-----------------------------+
SEE ALSO csh(1), echo(1), ksh(1), sh(1), tr(1), wc(1), attributes(5)NOTES
The -n option is a transition aid for BSD applications, and may not be supported in future releases.
SunOS 5.10 3 Aug 1994 echo(1B)