This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: strace on inetd (was RE: bash failed to initialize on telnet/rsh/ rlogin server)
- From: Christopher Faylor <cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 27 Mar 2002 19:20:19 -0500
- Subject: Re: strace on inetd (was RE: bash failed to initialize on telnet/rsh/ rlogin server)
- References: <718198F862F1D411B10F0002A50A4DB1059FE8E7@e90wwce3.dx.deere.com>
- Reply-to: cygwin at cygwin dot com
On Wed, Mar 27, 2002 at 02:20:35PM -0600, Polley Christopher W wrote:
>Are there more complete instructions to strace besides --help, the Cygwin
>user guide, or winsup/utils/utils.sgml (all essentially the same thing)?
If we had better documentation why would it be hidden?
The best documentation is the source code. In this case, the use of
strace -p would require that you do your debugging from an account which
had the ability to access the executing pid. If you are running inetd
from a privileged account and stracing from a user account that won't
work for hopefully obvious reasons.
Also, due to limitations in the Windows API, there is no way to strace a
forked process via strace -p. strace -p uses the DebugActiveProcess
function and there is no way to tell the process being debugged that you
need to follow CreateProcess calls.
cgf
--
Please do not send me personal email with cygwin questions.
Use the resources at http://cygwin.com/ .
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/