scp not shutting down in 2.1.1p4

[Lutz Jaenicke]

On Thu, Jul 20, 2000 at 05:19:02PM +0200, Kevin Steves wrote:
...
> write(1, "\n", 1) .............................................................. = 1
> close(3) ....................................................................... = 0
> write(6, "\0", 1) .............................................................. = 1
> read(7, "\0", 1) ............................................................... = 1
> exit(0) ........................................................................ WIFEXITED(0)
...


> stack trace "hung" scp process:
...
> 0xc01ed230 in _read_sys () from /usr/lib/libc.2
> (gdb) bt
> #0  0xc01ed230 in _read_sys () from /usr/lib/libc.2
> #1  0xc01f85e4 in read () from /usr/lib/libc.2
> #2  0x82a8 in atomicio (f=0x400026d2 <SD$endc+122>, fd=0, _s=0x7bff03c0 "C0664 53 X", n=1) at atomicio.c:46
> #3  0x625c in sink (argc=1, argv=0x7bff014c) at scp.c:702
> #4  0x4c08 in main (argc=1, argv=0x7bff014c) at scp.c:335

Thanks for your effort.
I have browsed through the scp.c source, but it seems I must understand
the rcp protocol first.
My impression from source() is, that the transfer is finished with '\0',
which would coincide with your trace of the calling scp.
I however did not find the corresponding check in sink(), which either
'return's from sink() or 'exit's the remote scp. I rather hangs in a
read, as both the calling ssh and the sshd wait the remote scp to exit...

Best regards,
	Lutz
-- 
Lutz Jaenicke                             Lutz.Jaenicke at aet.TU-Cottbus.DE
BTU Cottbus               http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik                  Tel. +49 355 69-4129
Universitaetsplatz 3-4, D-03044 Cottbus              Fax. +49 355 69-4153