In the process of testing a client/server set of programs a certain
condition leaves the server child process hanging. Is there a way to kill
the server child process and get a core dump?

--
Marshall Lake -- mlake [at] melake.erols.com -- http://melake.erols.com

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Marshall Lake wrote:

> In the process of testing a client/server set of programs a certain
> condition leaves the server child process hanging. Is there a way to kill
> the server child process and get a core dump?

kill -IOT <pid>

should do the job, as long as the process hasn't ignored that signal,
and it's resource limits allow the core dump to be created.

If the process ignores/catches all signals, then you're out of luck;
SIGKILL doesn't result in a core dump.

Also, if the process' resource limits don't allow the creation of a
core dump (RLIMIT_CORE, "ulimit -c"), you're out of luck. One process
can't change the resource limits of another.

--
Glynn Clements <glynn.clements [at] virgin.net>
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

> > In the process of testing a client/server set of programs a certain
> > condition leaves the server child process hanging. Is there a way to kill
> > the server child process and get a core dump?

> kill -IOT <pid>

Thanks.

I used kill -6 <pid>
kill -IOT resulted in:

kill: bad signal spec `IOT'

--
Marshall Lake -- mlake [at] melake.erols.com -- http://melake.erols.com

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html