On Sun, Jul 12, 2015 at 01:53:54PM +0200, Christian Weisgerber wrote:
> Sebastien Marie:
>
> > > --- tcpdump.c 18 Apr 2015 18:28:38 -0000 1.70
> > > +++ tcpdump.c 11 Jul 2015 20:35:11 -0000
> > > @@ -603,8 +603,10 @@ default_print_ascii(const u_char *cp, un
> > > printf("\n");
> > > for (i = 0; i < length; i++) {
> > > c = cp[i];
> > > - c = isprint(c) || isspace(c) ? c : '.';
> > > - putchar(c);
> > > + if (isprint(c) || c == '\t' || c == '\n' || c == '\r')
> >
> > does printing '\r' will allow overriding previously printed char on line ?
>
> Yes. I thought of this, but note that default_print_ascii() is
> only used for -A output, not for -X, and that all human-readable
> protocols (SMTP, SIP, ...), which are the ones where you might want
> to use -A in the first place, have \r\n line endings. If you need
> to see the exact bytes, use -X.
>
It makes sens. And it is the same as the previous behaviour (\r was
already printed).
OK semarie@
--
Sebastien Marie
