Sponsored Content
Full Discussion: memory fault
Top Forums Programming memory fault Post 302068794 by matrixmadhan on Tuesday 21st of March 2006 03:15:06 AM
Old 03-21-2006
be clear and specific in your posts.

core dump could arise due to many faults
and one such is illegal memory access.

Please mention the pt where you encounter that problem.
That would help to proceed further.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Memory Fault

I am using Unix OpenServer Release 5. When a run a application with user different to "Superuser" the application give me the following error: "Memory Fault - Core Dump". What's that mean? Thank you in advance. Roberto Veras. (1 Reply)
Discussion started by: robertoveras
1 Replies

2. Programming

Memory fault(coredump)

Dear All, I made a program which do some simple jobs like reading data from other process's shared memory and writing messages to the queues of other process. what happens is my program works fine and do all the task as expected but then then program ends it give Memory fault(coredump). I... (0 Replies)
Discussion started by: ralo
0 Replies

3. UNIX for Advanced & Expert Users

Memory fault in ql session

Hi, Am getting memory fault when i start ql session in SCO unix server. Can any one suggest the way to solve this issue. Thanks (0 Replies)
Discussion started by: param_it
0 Replies

4. Ubuntu

Memory fault(coredump)

Hey guys, I am new to the Linux world and have a question to post. When I ssh from a HP-UX machine to a ubuntu machine I get the following error message Memory fault(coredump) i.e. ssh 192.168.1.3 I get this message as shown below Memory fault(coredump) Can someone please explain... (2 Replies)
Discussion started by: fkaba81
2 Replies

5. UNIX for Dummies Questions & Answers

mysql memory fault

I (think I) installed MYSQL on a Red Hat box. When I try to start mysql I get a memory fault error. Any ideas on how to fix this? Here is some info that might help: My distro info $ cat /proc/version Linux version 2.4.21-40.ELsmp (bhcompile@hs20-bc1-7 .build.redhat.com) (gcc version 3.2.3... (0 Replies)
Discussion started by: wsetchell
0 Replies

6. UNIX for Advanced & Expert Users

Setui(0) memory fault

Hi i have this code that used to wrok fine in unix mp-ras. After the migration to linux suse i recompiled the script and now when it is executed i get a Memory fault (coredump) message. Does anybody knows why' what should I change? tks SCRIPT #include <stdio.h> #include <sys/types.h>... (1 Reply)
Discussion started by: mrodrig
1 Replies

7. Linux

Help with memory fault

We have migrated our application from HP UX to linux. The code is in 4gl and after migration it has started giving Memory fault while running a batch job. The trace shows segmentation fault after a series of recvfrom and sendto(DB read) sigsegv segmentation fault @ 0 0 killed by SIGSEGV The... (2 Replies)
Discussion started by: aimee
2 Replies

8. UNIX for Dummies Questions & Answers

Page Fault + Memory

I am not sure where to post this so i will put it in the newbie section. I have set up a bog standard debain 6, LAMP environment in the cloud. The specs 1 core at 2GH 2.5gb Memory running Jommla, with about 1.6K visitors a day. I am using AppFirst (appfirst.com) to monitor the... (2 Replies)
Discussion started by: waseem
2 Replies

9. Homework & Coursework Questions

Memory fault(coredump)

I am writing a program that copies a program and prints the program with a line count. this is the program I wrote: #include <stdio.h> main() { int c; int nl_cnt = 0; while((c = getchar()) != EOF){ if(c = '\n'){ nl_cnt++;... (3 Replies)
Discussion started by: heywoodfloyd
3 Replies

10. Solaris

M4000 Memory Fault

Hi Guys and Gals, Does anyone know how to track down a faulty DIMM on the memory board of an M4000? showhardconf tells me which board it is, but was wondering if there was a way to track it down to a DIMM? Thanks in advance Martin (5 Replies)
Discussion started by: callmebob
5 Replies
KGDB(1) 						    BSD General Commands Manual 						   KGDB(1)

NAME
kgdb -- kernel debugger SYNOPSIS
kgdb [-a | -f | -fullname] [-b rate] [-q | -quiet] [-v] [-w] [-d crashdir] [-c core | -n dumpnr | -r device] [kernel [core]] DESCRIPTION
The kgdb utility is a debugger based on gdb(1) that allows debugging of kernel core files. The options are as follows: -a Increase the annotation level. An annotation level of 1 features the historical -fullname option of gdb(1). This is useful when running kgdb in Emacs. The -f or -fullname options are supported for backward compatibility as well. -b rate Set the baudrate to rate. -q Suppress printing of the banner when the debugger starts. The -quiet form is supported for compatibility as well. -v Increase verbosity. -w Opens kmem-based targets in read-write mode. (This is identical to what --wcore used to do in previous gdb versions for FreeBSD.) -d crashdir Use crashdir instead of the default, /var/crash to locate kernel core dump files in. The name vmcore. plus the dump number will be appended to determine the actual dump file name. -c core Explicitly use core as the core dump file. -n dumpnr Use the kernel core dump file numbered dumpnr for debugging. -r device Use device to connect kgdb to for a remote debugging session. The -c, -n, and -r options are mutually exclusive. Optionally, the name of the kernel symbol file and the name of the core dump file can be supplied on the command-line as positional argu- ments. If no kernel symbol file name has been given, the symbol file of the currently running kernel will be used. If no core dump file has been specified through either of the options or the last command-line argument, /dev/mem will be opened to allow debugging the currently run- ning kernel. FILES
/dev/mem Default memory image to open if no core dump file has been specified. /var/crash Default directory to locate kernel core dump files. SEE ALSO
gdb(1) HISTORY
The kgdb utility first appeared in its current form in FreeBSD 5.3. BSD
October 11, 2006 BSD
All times are GMT -4. The time now is 11:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy