ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 10272] Propose enhancing how Wireshark reads preferences/r

Date: Thu, 10 Jul 2014 23:06:25 +0000

changed bug 10272

What Removed Added
Component GTK+ UI Dissection engine (libwireshark)

Comment # 1 on bug 10272 from
If this works on Linux but not OS X, it's probably a difference between the
Linux (GNU libc or whatever) and OS X (*BSD) standard I/O library routines, so
that Linux's libc treats either LF or CR-LF as a line ending and OS X's
doesn't.  I'd be a bit surprised to see such differences, however, as, on UN*X,
the standard I/O library routines don't, in general, make a distinction between
text and binary files; perhaps fgets() on Linux, for example, strips off
trailing CRs on Linux, which *might* not be forbidden by the Single UNIX
Specification.

The right thing to do might be to, if possible, ignore CR at the ends of lines
when reading *any* text file.  On Windows, files with CR-LF line endings
should, when read as text (the default mode with the standard I/O library
routines, and the mode we use when reading text files other than text-format
capture files), have just LF at the end of a line; on UN*X, files with CR-LF
line endings might, when read, include the CR at the end of a line and, if
stripping CRs in text-reading routines such as fgets() isn't explicitly
forbidden, might not include it, so ignoring it should work on all platforms.


You are receiving this mail because:
  • You are watching all bug changes.