SVN version, indicate that the SVN version is unknown. This puts back the fix
for bug 1413.
Add a new version.conf option for make-version which tell is "this is a build
from a release tarball." When that option is present do not try to use SVN
to determine the SVN version, just use whatever SVN information shipped in the
tarball.
If version.conf is present in the source tree (as it is only in the release
branches), deliver it in the source tarball but only after setting the "this
is a release tarball" option.
All of this means that that builds from release-branch tarballs will report
the SVN version of the release tarball rather than "unknown." This addresses
the issue reported in
http://ask.wireshark.org/questions/5376/wireshark-161-title-shows-svn-rev-unknown-from-unknown
Builds from trunk (including the source tarballs) will continue to report that
the SVN version is unknown. (Maybe that, too, should be changed?)
svn path=/trunk/; revision=38933
Fixes a problem on Windows wherein specifying a capture file
time duration for autostop or file-switching would stop
working after some period of time.
The reason:
GetTickCount returns DWORD (unsigned int) which
wraps "every 49.7 days";
and: The GetTickCount() return value was being stored in a time_t which is
int64 on Windows;
thus:
The test for elapsed time (using signed integers) didn't work correctly after
the time had wrapped.
Fixes Bug #6280: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6280
svn path=/trunk/; revision=38921
Fix problem with the decoding of the exception schedule. It was eating one
too many closing tags before exiting and causing the rest of the information to
fail to decode correctly.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6178
svn path=/trunk/; revision=38919
Fixes log-status and status-flags plus other BACnet decoding bugs
This patch fixes the log-status and status-flag decoding issues described in
this bug report. This patch also fixes the following items:
1) date-list decoding
2) time-synchronization-recipients decoding
3) decoding of UTF-8 character strings (when using character set 0)
4) event-parameter decoding
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5120
svn path=/trunk/; revision=38914
When context id is reused by another termination, initial packet containing $
(=choose one) is not added to context but belongs to context 0xfffffffe(context
id value used in wireshark for choose one). This affects context listing in
MEGACO packet contents and Telephony->Voip Calls listings for MEGACO.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6311
svn path=/trunk/; revision=38910
Wireshark improperly parsing 802.11 Beacon Country Information tag
From me:
Fix this issue (miss the optionnal Pad field for Country Tag)
svn path=/trunk/; revision=38878
Anders Broman