Search results

Crashtracker: investigate how we can coexist with libsegfault

Status: Open.

#700 In DataDog/libdatadog;

· danielsn opened on Oct 30, 2024

What topics should we include in the libdatadog developer guide?

questionFurther information is requestedFurther information is requested

Status: Open.

#596 In DataDog/libdatadog;

· ekump opened on Aug 23, 2024

[crashtracker] Limit size of files in the crashinfo

Status: Open.

#564 In DataDog/libdatadog;

· danielsn opened on Aug 1, 2024

[common] Unify FFI result types

Status: Open.

#563 In DataDog/libdatadog;

· danielsn opened on Aug 1, 2024

[Crashtracker]: simplify on fork

Status: Open.

#562 In DataDog/libdatadog;

· danielsn opened on Jul 31, 2024

[crashtracker] consistent naming convention for operations

Status: Open.

#561 In DataDog/libdatadog;

· danielsn opened on Jul 31, 2024

[crashtracker] Use same representation for crashtracker and profiler stacktraces

Status: Open.

#559 In DataDog/libdatadog;

· danielsn opened on Jul 31, 2024

[crashtracker] Publish crates to crates.io

Status: Open.

#557 In DataDog/libdatadog;

· danielsn opened on Jul 31, 2024

[crashtracker] rationalize config/metadata structs in API

Status: Open.

#556 In DataDog/libdatadog;

· danielsn opened on Jul 31, 2024

[crashtracker] Why is it that the emission of some data is immediately followed by a flush operation sometimes, but not always?

Status: Open.

#546 In DataDog/libdatadog;

· danielsn opened on Jul 23, 2024

[FEATURE] Build system handles different feature configurations

Status: Open.

#353 In DataDog/libdatadog;

· r1viollet opened on Mar 12, 2024

crashtracker: emit additional_stacktraces to telemetry

Status: Open.

#344 In DataDog/libdatadog;

· danielsn opened on Mar 5, 2024