1.\" Copyright (c) 1985, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" %sccs.include.redist.man% 5.\" 6.\" @(#)trsp.8 8.1 (Berkeley) 06/06/93 7.\" 8.Dd 9.Dt TRSP 8 10.Os BSD 4.2 11.Sh NAME 12.Nm trsp 13.Nd transliterate sequenced packet protocol trace 14.Sh SYNOPSIS 15.Nm trsp 16.Op Fl a 17.Op Fl s 18.Op Fl t 19.Op Fl j 20.Op Fl p Ar hex-address 21.Oo 22.Ar system Op Ar core 23.Oc 24.Sh DESCRIPTION 25.Xr Trpt 26interrogates the buffer of 27.Tn SPP 28trace records created 29when a socket is marked for 30.Dq debugging 31(see 32.Xr setsockopt 2 ) , 33and prints a readable description of these records. 34When no options are supplied, 35.Nm trsp 36prints all the trace records found in the system 37grouped according to 38.Tn SPP 39connection protocol control 40block 41.Pq Tn PCB . 42The following options may be used to 43alter this behavior. 44.Bl -tag -width Ds 45.It Fl a 46In addition to the normal output, 47print the values of the source and destination 48addresses for each packet recorded. 49.It Fl j 50Just give a list of the protocol control block 51addresses for which there are trace records. 52.It Fl p 53Show only trace records associated with the protocol 54control block at the given address, 55.Ar hex-address . 56.It Fl s 57in addition to the normal output, 58print a detailed description of the packet 59sequencing information. 60.It Fl t 61in addition to the normal output, 62print the values for all timers at each 63point in the trace, 64.El 65.Pp 66The recommended use of 67.Nm trsp 68is as follows. 69Isolate the problem and enable debugging on the 70socket(s) involved in the connection. 71Find the address of the protocol control blocks 72associated with the sockets using the 73.Fl A 74option to 75.Xr netstat 1 . 76Then run 77.Nm trsp 78with the 79.Fl p 80option, supplying the associated 81protocol control block addresses. If there are 82many sockets using the debugging option, the 83.Fl j 84option may be useful in checking to see if 85any trace records are present for the socket in 86question. 87.Pp 88If debugging is being performed on a system or 89core file other than the default, the last two 90arguments may be used to supplant the defaults. 91.Sh FILES 92.Bl -tag -width /dev/kmem -compact 93.It Pa /vmunix 94.It Pa /dev/kmem 95.El 96.Sh SEE ALSO 97.Xr netstat 1 , 98.Xr setsockopt 2 99.Sh DIAGNOSTICS 100.Bl -tag -width Ds 101.It Sy no namelist 102When the system image doesn't 103contain the proper symbols to find the trace buffer; 104others which should be self explanatory. 105.Sh BUGS 106Should also print the data for each input or output, 107but this is not saved in the race record. 108.Pp 109The output format is inscrutable and should be described 110here. 111.Sh HISTORY 112The 113.Nm 114command appeared in 115.Bx 4.3 . 116