core from a running process

[gaf at blu.org (Jerry Feldman)]

I think that gdb is your best option. You can specify a process id. (gdb 
<file> pid). 
The first thing to do is to try to determine which process is causing the 
problem. If the process is in a loop, then you can see it eating CPU time 
(using top(1)). 

Or, run gdb on each of its processes, get a stack dump, or look at the 
state of some variables.  
On 3 Sep 2002 at 9:09, FRamsay at castelhq.com wrote:

> Does anyone know of a way to get a core from a running process without
> crashing the process?  I have a process
> that occasionally stops responding but doesn't actually crash.  Worse this
> only happens at one client site and
> I can't reproduce it in the office, so I can't attach dbg to it.  To
> complicate matters the application spawns several
> other processes so I don't know which one is causing the problem :(     So
> does anyone know a very simple way I
> can get core file, and it has to be _very_ simple because I have to talk
> the client through it over the phone.
> 
>                          -fjr
> 
> 
> Frank Ramsay
> Systems Programmer
> Castel, Inc
> 14 Summer St, 3rd Floor
> Malden, MA 02148
> (781) 324-0140 (voice)
> (781) 324-0277 (fax)
> Emal: framsay at castel.com
> 
> 
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss


-- 
Jerry Feldman <gaf at blu.org>
Associate Director
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9