10-12-2012
Thanks for replies
1. As explained in first post of thread , using normal gdb backtrace comand could not helpful , since i know Segmentation fault log , my question is not how i could catch the segmentation fault error log or fix it , since i know how.
my question is , If segmentation fault error occur more than 12 times , my environment (or maybe my kernel would crash) it could be kernel bug with my stb , Therefore , using -g and catch the first SEGV is not my desire (i know even the fix for this SEGV) but i deliberately , let it to be , in order to investigate Kernel (or environment) crash
if i use -g option and use gdb , before i could achieve to investigate Kernel (or environment) crash , i would get Segmentation fault (which is not as my desire , since it prevent me to know , why kernel would crash...
2. i compiled polo , with the cc option : -ggdb
could somebody please tell me what is the difference beetween -g and -ggdb in cc option?
10 More Discussions You Might Find Interesting
1. Programming
I have written a program which takes a directory as command line arguments and displays all the dir and files in it.
I don't know why I have a problem with the /etc directory.It displays all the directories and files untill it reaches a sub directory called peers which is in /etc/ppp/peers.the... (4 Replies)
Discussion started by: vijlak
4 Replies
2. AIX
Hi ,
During execution a backup binary i get following error
"Program error 11 (Segmentation fault), saving core file in '/usr/datatools"
Riyaz (2 Replies)
Discussion started by: rshaikh
2 Replies
3. Linux
Hi,
on a linux Red HAT(with Oracle DB 9.2.0.7) I have following error :
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Segmentation fault
What does it mean ? And the solution ?
Many thanks. (0 Replies)
Discussion started by: big123456
0 Replies
4. Programming
What is segmentation fault(core dumped) (1 Reply)
Discussion started by: gokult
1 Replies
5. Programming
I'm getting a segmentation fault. I'm new to Linux programming. Thanks so much for all of your input.:eek:
#include </usr/include/mysql++/mysql++.h>
#include <stdio.h>
#include <iostream>
#include <sstream>
#include <string.h>
using namespace std;
int outputToImport(const char*... (1 Reply)
Discussion started by: sepoto
1 Replies
6. Programming
This code is causing a segmentation fault and I can't figure out why. I'm new to UNIX and I need to learn how to avoid this segmentation fault thing. Thank you so much. Thanks also for the great answers to my last post.:):b:
int main()
{
mysqlpp::Connection conn(false);
if... (3 Replies)
Discussion started by: sepoto
3 Replies
7. Programming
Hello everyone,
I am using the debugger from C++ and these are the message I got:
Program received signal SIGSEGV, Segmentation fault.
0x0040cc0e in malloc_consolidate (av=0x4ff3c0) at malloc.c:5169
in malloc.c
I don't know if the problem is cause i'm trying to acess an invalid memory... (1 Reply)
Discussion started by: juliecf5
1 Replies
8. Homework & Coursework Questions
this is a network programming code to run a rock paper scissors in a client and server.
I completed it and it was working without any error. After I added the findWinner function to the server code it starts giving me segmentation fault.
-the segmentation fault is fixed
Current problem -Also... (3 Replies)
Discussion started by: femchi
3 Replies
9. UNIX for Dummies Questions & Answers
I am using scientific linux. In the directory user/project/Build, after I ran 'make' to compile and link all the cpp files,I had no problems. But then, when I went to directory user/run/run.sh, which runs the project binary in user/project/Build/bin/project, I get a segmentation fault error. In... (1 Reply)
Discussion started by: larry burns
1 Replies
10. Programming
Oddities with gcc, 2.95.3 for the AMIGA and 4.2.1 for MY current OSX 10.14.1...
I am creating a basic calculator for the AMIGA ADE *NIX emulator in C as it does not have one.
Below are two very condensed snippets of which I have added the results inside the each code section.
IMPORTANT!... (11 Replies)
Discussion started by: wisecracker
11 Replies
LEARN ABOUT NETBSD
savecore
SAVECORE(8) BSD System Manager's Manual SAVECORE(8)
NAME
savecore -- save a core dump of the operating system
SYNOPSIS
savecore [-fvz] [-N system] [-Z level] [directory]
savecore -c [-v] [-N system]
savecore -n [-v] [-N system]
DESCRIPTION
When the NetBSD kernel encounters a fatal error, the panic(9) routine arranges for a snapshot of the contents of physical memory to be writ-
ten into a dump area, typically in the swap partition.
Upon a subsequent reboot, savecore is typically run out of rc(8), before swapping is enabled, to copy the kernel and the saved memory image
into directory, and enters a reboot message and information about the core dump into the system log. If a directory is not specified, then
/var/crash is used.
The kernel and core file can then be analyzed using various tools, including crash(8), dmesg(8), fstat(1), gdb(1), iostat(8), netstat(1),
ps(1), and pstat(8), to attempt to deduce the cause of the crash.
Crashes are usually the result of hardware faults or kernel bugs. If a kernel bug is suspected, a full bug report should be filed at
http://www.netbsd.org/, or using send-pr(1), containing as much information as possible about the circumstances of the crash. Since crash
dumps are typically very large and may contain whatever (potentially confidential) information was in memory at the time of the crash, do NOT
include a copy of the crash dump file in the bug report; instead, save it somewhere in the event that a NetBSD developer wants to examine it.
The options are as follows:
-c Only clears the dump without saving it, so that future invocations of savecore will ignore it.
-f Forces a dump to be taken even if the dump doesn't appear correct or there is insufficient disk space.
-n Check whether a dump is present without taking further action. The command exits with zero status if a dump is present, or with
non-zero status otherwise.
-N Use system as the kernel instead of the default (returned by getbootfile(3)). Note that getbootfile(3) uses secure_path(3) to
check that kernel file is ``secure'' and will default to /netbsd if the check fails.
-v Prints out some additional debugging information.
-z Compresses the core dump and kernel (see gzip(1)).
-Z level Set the compression level for -z to level. Defaults to 1 (the fastest compression mode). Refer to gzip(1) for more information
regarding the compression level.
savecore checks the core dump in various ways to make sure that it is current and that it corresponds to the currently running system. If it
passes these checks, it saves the core image in directory/netbsd.#.core and the system in directory/netbsd.# (or in
directory/netbsd.#.core.gz and directory/netbsd.#.gz, respectively, if the -z option is used). The ``#'' is the number from the first line
of the file directory/bounds, and it is incremented and stored back into the file each time savecore successfully runs.
savecore also checks the available disk space before attempting to make the copies. If there is insufficient disk space in the file system
containing directory, or if the file directory/minfree exists and the number of free kilobytes (for non-superusers) in the file system after
the copies were made would be less than the number in the first line of this file, the copies are not attempted.
If savecore successfully copies the kernel and the core dump, the core dump is cleared so that future invocations of savecore will ignore it.
SEE ALSO
fstat(1), gdb(1), gzip(1), netstat(1), ps(1), send-pr(1), crash(8), dmesg(8), iostat(8), pstat(8), rc(8), syslogd(8), panic(9)
HISTORY
The savecore command appeared in 4.1BSD.
BUGS
The minfree code does not consider the effect of compression.
BSD
September 13, 2011 BSD