| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Structure change in asterix-specs, revision 3ab3bb3.
Rule type is generalized and it now also includes a default value.
|
|
|
|
|
|
|
|
|
|
Use directory-level suppressions where needed.
|
|
Add an initial Clang-Tidy configuration file which checks for recursion
and various clang analyzer issues.
Run Clang-Tidy in the "Clang + Code Checks" merge request job.
Add NOLINT suppressions where needed in wsutil, epan, and lemon.
|
|
|
|
[skip ci]
|
|
|
|
|
|
Many of the generated "const" fields can be made static. For local variables,
this means that the compiler will no longer emit code to allocate the structure
on the stack and initialize it upon each function entry -- 29 kBytes of code in
total gets removed by this change -- which is surely a performance win when
dissecting this protocol.
Interestingly, libwireshark.so ends up growing overall due to the addition of
52 kBytes of relocation entries to patch up references within the relocatable
read-only data section. Clearly the generated code was more space-efficient
than the relocation entries...
|
|
mesa version 24.0-branchpoint-1188-gc3062e3402f
xcbproto version xcb-proto-1.16.0-2-g1388374
Add GestureClass to the unused structures list.
|
|
|
|
|
|
The DCM tag/status/uid lookup tables are only ever read. const-ifying them
moves about 220 kBytes of data to a read-only data section.
packet-dcm.h was regenerated using the make-packet-dcm.py script.
|
|
The Well-Known Frames of Reference data have moved to Table A-2, so the script
is updated to integrate the data from that table into the UID list.
Ran "tools/make-packet-dcm.py > epan/dissectors/packet-dcm.h".
|
|
MR !14295 ran into trouble with the license checker because three added lines
in tools/make-packet-dcm.py moved the important piece of text outside the
150-line window in which it was checking.
This change maintains the status quo by expanding the window to 160 lines.
|
|
|
|
|
|
One of these modifies a field name ("hart_ip.pt.rsp.transducer_serail_number"
in packet-hartip.c), a few are in text displayed for fields (in packet-nvme.c)
or for unknown fields (in packet-oer.c and packet-per.c), one is in a
preprocessor macro (in packet-cip.[ch]), and the rest are all in comments.
arry -> array
authos -> authors
compatability -> compatibility
contigous -> contiguous
dispaly -> display
erorr -> error
filed (where it was obviously incorrect) -> field or filled
hueristic -> heuristic
regsiter -> register
serail -> serial
|
|
|
|
This moves 15 kBytes of data to a read-only data section.
|
|
This moves 54 kBytes of data to a read-only data section.
|
|
PI_RECEIVE is for indications from the process of receiving packets,
such as CRC errors, short/long frame indications, etc..
PI_INTERFACE is for indications from an interface (other than receive
indications), such as out-of-buffrs indications, hardware errors,
changes in link speed, etc..
See !14177 for some discussion of this.
|
|
|
|
Some of the functions in proto.c when handling a FT_BOOLEAN field
allow it to be part of a 64 bit unsigned integer with a 64 bit
bitmask. Other functions do not. Some of the functions start out
allowing a 64 bit bitmask and then switch to casting the value to
a 32 bit unsigned integer (but others don't.) Consistently allow
a boolean to be extracted using a 64 bit bitmask by changing the
various proto_tree_add_boolean functions to allow a 64 bit unsigned
integer value parameter.
There was only one function adding a boolean that already took
a 64 bit value, proto_tree_add_boolean_bits_format_value64, a
counterpart of proto_tree_add_boolean_bits_format_value. It was
never used anywhere and not WS_DLL_PUBLIC, so it is safe to remove
in favor of having the latter take a uint64_t.
Note that _proto_tree_add_bits_format_value, as a comment says:
"does not receive an actual value but a dimensionless pointer to that value.
For this reason, the type of the header field is examined in order to determine
what kind of value we should read from this address.
The caller of this function must make sure that for the specific header field
type the address of a compatible value is provided."
Both proto_tree_add_boolean_bits_format_value and
proto_tree_add_boolean_bits_format_value64 called that function, one
passing a pointer to a guint32 as a void*, the other passing a
pointer to a guint64. In both cases it was cast to a guint32*, which
was less than ideal in the value64 case. Fix that.
This is related to #19552, as it is necessary in order to add support
for passing a UInt64 value to a boolean field (as oppposed to extracting
it directly from the tvb.)
|
|
Define VCS_NUM_COMMITS and VCS_COMMIT_ID in vcs_version.h. Use them to
return the Logray version in get_lr_vcs_version_info and use that where
appropriate. Rename VCSVERSION to VCS_VERSION.
|
|
"plus" means that we built from libssh commit 6f1b1e76bb38b, which
includes 1.10.6 plus an IPv6 address parsing fix.
|
|
|
|
|
|
Install Falco libs (libsinsp and libscap) and their dependencies if
FALCO_LIBS_VERSION is defined.
[skip ci]
|
|
|
|
|
|
|
|
|
|
|
|
The list of TCP/UDP/SCTP/DCCP port numbers never needs to be modified. This
moves ~150 kBytes of data to a read-only data section.
|
|
This moves ~620 kBytes of data into the read-only data section.
|
|
Use `set -e` and remove a bunch of no-longer-needed `|| exit 1`s. Make
sure we pass `--fail-with-body` to curl, and that we have a version of
curl that supports that option. Fix other issues that `set -e` turned
up.
[skip ci]
|
|
|
|
|
|
Pass in our installation prefix at build time, which is required for
prefixes other than /usr/local. Fix a few ShellCheck warnings.
[skip ci]
|
|
|
|
|
|
This fixes a few recent CVEs that don't appear to affect us, but better
safe than sorry.
Fix some shellcheck warnings in the GnuTLS and related functions.
|
|
Use command substitution instead of backticks. Use an array for our
build-time make options. Fixup some dynamically sudo-ized commands.
[skip ci]
|
|
Add a `-p` option, which lets you specify an installation prefix for
software libraries. Ruby gems and Python modules (Asciidoctor and
pytest) still install into their default locations.
[skip ci]
|
|
|
