coreadm diasble a process from core dumping Post: 302134419

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Getting core id, physical id of running process

Hi All, I need a help. I need to know: 1. the individual core id, physical id of a running process on multicore inside a program. The system file /proc/cpuinfo shows all the ids of all the processes. But I need to know runtime, what exact core id and physical id , the running process has....

2. UNIX for Dummies Questions & Answers

How to force core dump of a process

We have an application that terminates with segmentation violation errors in the logs. No source code is available since this is a third party software that is way past its maintenance life cycle. Under these circumstances is there a way to force a core dump of the process for further analysis?? ...

3. Programming

strcat() dumping core

strcat dumping core in the situation like main() { char* item; char* p=sat_item; char type; item=(char*) malloc(strlen(p)); strncpy(type,p,4); type='\0'; strcat(item,type); //dumping core } I couldn't get why strcat dumping core?

4. HP-UX

script running with "ksh" dumping core but not with "sh"

Hi, I have small script written in korn shell. When it is called from different script, its dumping core, but no core dump when we run it standalone. And its not dumping core if we run the script using "/bin/sh" instead of "ksh" Can some body please help me how to resolve this issue. ...

5. Filesystems, Disks and Memory

Issue with coreadm utility

Hi all, The core files are moved to a partition in my server using the coreadm utility. But the owner of the core files created is root. So other users are not having privillege to analys the same. -rw------- 1 root root 56512875 Apr 27 17:05 tpm007_upd_local.N820.114.16281.core...

6. Programming

how to monitor the child process on which cpu core

Hi all. Sorry to express my questions wrongly in my early post,I repost my question again here. My pc has dual core, I wirte an application with two process, parents process and child process. My quetion is how to realize :if the child process is on core 0,it will tell me I'm on core 0,if it...

7. Red Hat

Core Dumping?

How to now if the server is core dumping into the same filesystem?

8. Solaris

Where does the command coreadm -e log

I ran the commad coreadm -e log. Does anybody know where this file went on a Solaris 10 system? I checked in the current working directory and I don't see a file called in the directory. I also checked /var/core and I didn't see a log there.

9. Shell Programming and Scripting

Get the process/thread running on which core

I use top -H -p 1256 to show process 1256, and then press "f" then press "j" to display it is running on which core, is there a better mothed, I want to be automated to get this

10. Solaris

Assign a process to a core on start

Hi, In Ubuntu it is possible to start a process in a specified core using taskset command (taskset 0 myproc it will execute myproc in core 0). I know it is possible a process(pid) can bind to a core using pbind. But my requirement is to start a process in a specified core. How it is...

LEARN ABOUT FREEBSD

kgdb

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