On Thu, 21 Nov 1996, Brad Spencer wrote:

   > I was able to reproduce this on a NetBSD/i386 which is some weeks old
   > and on NetBSD/alpha with a original disk image which was a couple of
   > weeks old.  It didn't happen on a NetBSD/sparc or a NetBSD/sun3 which
   > are from source only a couple of days old.
   > 
   > To find out what arguments are being passed to rsh I replaced it with
   > a shell script which writes the argument list to a file.  The file was
   > empty which leads one to suspect that the library routine fiddles with
   > the argument list or some such other thing.  GNU cpio attempts to find
   > the rsh program by execl'ing it from several absolute pathnames all
   > with the same arguments.

   This agrees with my analysis completely. I think the next step is to
   use gdb on it and start taking apart stack frames. Ugh!

   cjs

   Curt Sampson    cjs@portal.ca		Info at http://www.portal.ca/
   Internet Portal Services, Inc.	
   Vancouver, BC   (604) 257-9400		De gustibus, aut bene aut nihil.


I started to do that in cpio, but that particular call is contained in
a forked child and I don't believe debuggers, in general, can follow
across forks.  I have not been able to revisit this again.




Brad Spencer - brad@anduin.eldar.org   http://anduin.eldar.org