Hi,
I am trying to analyze one core file on my RHEL 6.5, but I am getting below error related to the core file. So I am not getting any stack trace about the crash.
Why gdb is complaining about the core size? There is enough space left for core files with ulimit unlimited set for core file.
How to fix this kind of error or problem related to gdb? Is it a known bug in gdb on higher version of linux kernel?
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... (2 Replies)
I'm trying to use the GDB debugger and DDD to debug 64bit code. It seems that the AIX toolkit gdb version 6.0 works with 64bit code. But the ddd tool when running gdb gives the following errors :
Starting program: <my binary> <my params>
warning: "": not in executable format: There is an input... (2 Replies)
Hi all,
One fine day one of the services in our prod server started core dumping and then the core file was ftp'd to our test server , to debug we used gdb with the executable which we had but we could not get the function names ( maybe due to missing symbols ) How do i solve this ... (1 Reply)
Hi ,
Any gdb user could see my problem.
Let me describe what i want to do.
i have a test utility to send message to running process.
My interest is to go through to functions calls when my test case starts.
In a simple way i want have a code walk for a particular scenario of a test... (1 Reply)
hi all,
I am having set of core dumps obtained from client server. Now i am trying to read them but unable to do so.
I have few queries:
1. Core dumps were generated on some xyz server and copied to my unix virtual. Can I read them as text here?
2. I tried installing gdb-7.3 but when i fire... (0 Replies)
I have added some code in my file.
I have created executable rpm file of our code and also I have created debuginfo and debugsource files and installed all three.
But when I debug in gdb I see the the code changes in soucre file. But the break point does not hit at that place as if it did not... (1 Reply)
Hello
I have built our application on AIX 7.1 as a 64 bit application.
My queries are as follows:
Can a 32bit gdb (v7.6) and ddd (data display debugger - v3.3.12), debug a 64bit executable ?
If I have a small 64bit a.exe executable that seems to work.
If I have a more complicated executable... (4 Replies)
would like to know best guide or document for gdb for different architectures x86 , power pc etc..
would like to understand how to debug segmentation faults because of stack corruption ..
understand utilities ELF , objdump etc..
please guide me (1 Reply)
Hi ,
could someone suggest best reference for core file understanding , analysis , debugging for different architectures
like what registers represent what in a architecture specific core ..
how to get maximum information out of corrupted core
different tools and how they work and how to... (1 Reply)
Discussion started by: Gopi Krishna P
1 Replies
LEARN ABOUT ULTRIX
savecore
savecore(8) System Manager's Manual savecore(8)Name
savecore - save a core dump of the operating system
Syntax
/etc/savecore [ options ] dirname [ system ] [ corename ]
Description
The command is meant to be called near the end of the file. The command saves the core dump of the system (assuming one was made) and
writes a reboot message in the shutdown log.
The command checks the core dump to be certain it corresponds with the current running ULTRIX. If it does, it saves the core image in the
file dirname/vmcore.n and saves the namelist in the file dirname/vmunix.n. The trailing .n in the pathnames is replaced by a number which
increments each time is run in that directory.
After saving the core and namelist images, will save the error logger buffer into a predetermined file. The error logger buffer contains
information about why the crash occurred. After completes, the daemon will extract the error logger file and translate its contents into a
form familiar to the program.
Before writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the filesystem that
contains dirname than the number obtained from the file, a core dump is not done. If the file does not exist, savecore always writes out
the core file (assuming that a core dump was taken).
The command also writes a reboot message in the shut down log. If the system crashed as a result of a panic, also records the panic string
in the shut down log.
For partial crash dumps, creates a sparse core image file in dirname/vmcore.n. If this sparse core image file is copied or moved to
another location, the file expands to its true size which can take too much file system space. Hence, to copy or move sparse core image
files, you must use the command. The command has a conversion option to create sparse output files.
Options-c Clears the core dump. This option is useful when the core dump is corrupted in a way that will not allow to save it safely. Use the
option with caution, because once it clears the core dump, the core dump cannot be retrieved.
-d dumpdev dumplo
Specifies the dump device and the dump offset when running on a system image other than the currently running system image. The pro-
gram assumes that the running system image is and it reads the dump device and dump device offset are different in the system image
that crashed, the option provides the correct dump device and dump device offset.
-e Saves only the error logger buffer into a file. If used, core or namelist images are not saved.
-f corename
Takes the i corefile name as the file from which to extract the the crash dump data instead of the default dump device. This option
is used only for diskless workstations.
If the core dump was from a system other than /vmunix, the name of that system must be supplied as system. The program assumes that the
running image is
After successful completion, the core dump is cleared. Also, a message is written in the file which tells whether the dump succeeded or
failed.
Files
Shut down log
Current running ULTRIX system
See Alsodd(1), uerf(8)savecore(8)