Skip to content

Conversation

@rabbitstack
Copy link
Owner

What is the purpose of this PR / why it is needed?

Resolve the thread start address to its respective symbol name and the module from which the function call is originated.

What type of change does this PR introduce?


Uncomment one or more /kind <> lines:

/kind feature (non-breaking change which adds functionality)

/kind bug-fix (non-breaking change which fixes an issue)

/kind refactor (non-breaking change that restructures the code, while not changing the original functionality)

/kind breaking (fix or feature that would cause existing functionality to not work as expected

/kind cleanup

/kind improvement

/kind design

/kind documentation

/kind other (change that doesn't pertain to any of the above categories)

Any specific area of the project related to this PR?


Uncomment one or more /area <> lines:

/area instrumentation

/area telemetry

/area rule-engine

/area filters

/area yara

/area event

/area captures

/area alertsenders

/area outputs

/area rules

/area filaments

/area config

/area cli

/area tests

/area ci

/area build

/area docs

/area deps

/area other

Special notes for the reviewer


Does this PR introduce a user-facing change?


@rabbitstack rabbitstack force-pushed the thread-start-address-symbol branch from 1a529d0 to 02ca983 Compare December 11, 2024 19:22
Resolve the thread start address to its respective
symbol name and the module from which the function
call is originated.
@rabbitstack rabbitstack force-pushed the thread-start-address-symbol branch from 02ca983 to 62b2ff1 Compare December 12, 2024 20:20
@rabbitstack rabbitstack merged commit efc84b3 into master Dec 15, 2024
6 checks passed
@rabbitstack rabbitstack deleted the thread-start-address-symbol branch December 15, 2024 12:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants