In the last episode (Sep 15), Vadim Belman said:
> It seem like I got a NFS-related bug here where a httpd process
> hung in a uninterruptable wait (a disk operation, most likely). In order to
> locate the problem I need the process' stack trace first.
>
> gdb doesn't attach to the process for obvious reasons. Making a
> crashdump doesn't inspire me at all.
>
> The question is: is there a way of working with /proc entries? I.e.
> is it possible to get all what I need from, say, /proc/<PID>/mem?
You can run "gcore <pid>" to generate a coredump from a running
program. I do this all the time to programs that I *don't* want to
attach directly to with gdb.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
