In fact, there's no problem at all under any linux system, I can use it very well under OpenSUSE, Fedora, or Ubuntu.
No offence V3l0, I mean the answer is not an easy one to have and blockMesh is above reproach.
On sgi-Irix6.5, after a core dump, I was adviced to perform a "strace", but I got the following information:
ERROR: tracer already exists
what shall I do now?
I am justing wandering, dear experts, what is the best way to locate the problem, to diagnose the diseases?
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)
Hi friends,
Can core file be deleted if there is no need for any one to use it for debugging ?
What should be the setting for a person who has root access to the solaris system ?
thanks in advance
Veera (2 Replies)
hello all,
I have same core like below:
lsav@GINTINGsmsc1/var/opt/GINTING/cores/SLF $ pstack core
core 'core' of 26799: /opt/GINTING/bin/SLF -poolSize 520000
pstack: warning: librtld_db failed to initialize; symbols from shared libraries will not be available
----------------- lwp# 1 ... (1 Reply)
Hi All,
May be it is a stupid question, but, I would like to know what is the advantage using a core dump file at the moment of debugging using gdb.
I know a core dump has information about the state of the application when it crashed, but, what is the difference between debugging using the... (2 Replies)
hi,
using core file ( stripped version of binary) i'm able to get backtrace. but i'm unable to figure out the root cause by looking at the code.
core file has been generated by SEGV. i'm able to disassemble the functions but i do not know how to interpret it. pls suggest.
thanks, (2 Replies)
1. The problem statement, all variables and given/known data:
When looking for corefiles, include any file with core in its name. (Some UNIX/Linux systems add the PID of the process that created the core to reduce the chances of overwriting an already existing core file that might be needed. The... (6 Replies)
Hi,
Regarding core dump on HP-UX.
more /etc/rc.config.d/savecrash
#!/sbin/sh
# @(#) $Revision: 80.1 $
# Savecrash configuration
#
#
# SAVECRASH: Set to 0 to disable saving system crash dumps.
SAVECRASH=1
# SAVECRASH_DIR:Directory name for system crash dumps. Note: the... (2 Replies)
Hi
I am using Linux and I have Java as well as C++ services running on it.
The ulimit -c is set to around 400Mb.
Whenever any of the service fails they produce a core file.(Actual size of core could be greater than 400Mb).
Whenever my Java service fails I get a core file of size 400Mb... (1 Reply)
Hi
I am using Linux and I am using Java as well as C++ services running on it.
The ulimit -c is set to around 400Mb.
Whenever any of the service fails they produce a core file.(Actual size of core could be greater than 400Mb).
Whenever my Java service fails I get a core file of size 400Mb... (3 Replies)
Discussion started by: Raj999
3 Replies
LEARN ABOUT OSX
gcore
gcore(1) User Commands gcore(1)NAME
gcore - get core images of running processes
SYNOPSIS
gcore [-pgF] [-o filename] [-c content] process-id...
DESCRIPTION
The gcore utility creates a core image of each specified process. By default, the name of the core image file for the process whose process
ID is process-id will be core.process-id.
OPTIONS
The following options are supported:
-c content Produces core image files with the specified content. The content description uses the same tokens as in coreadm(1M). The
-c option does not apply to cores produced due to the -p or -g flags.
-F Force. Grabs the target process even if another process has control.
-g Produces core image files in the global core file repository with the global content as configured by coreadm(1M). The com-
mand will fail if the user does not have permissions to the global core file repository.
-o filename Substitutes filename in place of core as the first part of the name of the core image files. filename can contain the same
tokens to be expanded as the paths in coreadm(1M).
-p Produces a core image file in the process-specific location with the process-specific content for each process as config-
ured by coreadm(1M). The command will fail if the user does not have permissions to the per-process core file repository.
OPERANDS
The following operand is supported:
process-id process ID
EXIT STATUS
The following exit values are returned:
0 On success.
non-zero On failure, such as non-existent process ID.
FILES
core.process-id core images
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWtoo |
+-----------------------------+-----------------------------+
|Interface Stability |See below. |
+-----------------------------+-----------------------------+
Command Syntax is Evolving. Output Format(s) are Unstable.
SEE ALSO kill(1), coreadm(1M), setrlimit(2), core(4), proc(4), attributes(5)NOTES
gcore is unaffected by the setrlimit(2) system call using the RLIMIT_CORE value.
SunOS 5.10 11 Feb 2004 gcore(1)