Tags: oxidecomputer/usdt
Tags
`dladdr(3c)` doesn't exist on Windows (#163) * `dladdr(3c)` doesn't exist on Windows - Don't use any dynamic loading constructions on Windows - Add CI target for Windows * Set RUST_BACKTRACE=1 for CI in an env key * Fixup use declarations * Exclude compiler error message tests from unsupported platform tests * use cfg(unix)
Adds support for translating double-underscores to dashes (#51) * Adds support for translating double-underscores to dashes - Any `__` in provider or probe names is now translated into `-`, inline with how DTrace probes are renamed in C, and to support the convention. - Small doc fixes * Update docs further with conditional-compilation suggestions * Update trybuild output
Bumps versions for release (#37) - `usdt-impl`: 0.1.12 -> 0.1.13 - `usdt-macro`: 0.1.13 -> 0.1.14 - `usdt-attr-macro`: 0.1.3 -> 0.1.4 - `usdt`: 0.1.17 -> 0.1.18 Also replaces exact version dependencies on other crates in the workspace. This was moved earlier, but should not have been.
Add default features to usdt-impl crate, fix name-length max (#32) This fixes an annoying issue related to feature-detection. Specifically, it seems that we need the `usdt-impl` crate to specify the `asm` feature as a default for the `default-features = false` bit in the top-level `usdt` crate to work. Without this, it's not clear why, but the `usdt-impl/asm` feature may or may not be selected dependending on how consumers of the `usdt` crate set their feature flags. Note that this also means _any_ crate that names `usdt-impl` as a dep, including the macro crates, must specify `default-features = false`. This also fixes a bug where long names sent to DTrace result in an EINVAL. Names like the provider are limited in length, usually to 64 or 128 characters (including the null-terminator). This ensures that pulling out the probe records, we truncate the strings we send over to DTrace via ioctl(2) are no longer than the maximum. This also bumps the version numbers, in preparation for a release.