Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugger step and follow commands #340

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

bazsi
Copy link
Member

@bazsi bazsi commented Oct 13, 2024

This PR adds multiple modes of operation to the debugger. Previously, we only had the "continue" command, that would run until the next LogPipe element and then stop there for inspecting the state.

This PR adds multiple debugger commands to continue with the evaluation:

  • step: run the config until the next LogPipe, may switch to a different message
  • continue: run the config until the next explicit breakpoint, there's no mechanism to set a breakpoint for now, so this essentially will run the configuration until stopped with Ctrl+C
  • follow: run the configuration, but only following the current message. Stops at the next LogPipe
  • trace: run the configuration and display timing information for the current message.

This sits on top of #546

The next for this PR is to add a breakpoint mechanism and also to make it possible to stop on filterx expressions.

@bazsi bazsi force-pushed the debugger-follow-command branch 3 times, most recently from a36329b to d1d8188 Compare October 27, 2024 11:30
@bazsi bazsi force-pushed the debugger-follow-command branch from d1d8188 to bfd41fc Compare December 10, 2024 11:10
@bazsi bazsi mentioned this pull request Dec 10, 2024
@bazsi bazsi force-pushed the debugger-follow-command branch from bfd41fc to 5c8539a Compare March 18, 2025 09:02
@bazsi bazsi force-pushed the debugger-follow-command branch from 5c8539a to 261e471 Compare March 18, 2025 09:26
bazsi added 11 commits March 20, 2025 08:39
Instead of using "NULL" as the indicator for the end of the lines to print,
just pass the number of entries in the lines array.

Signed-off-by: Balazs Scheidler <balazs.scheidler@axoflow.com>
Signed-off-by: Balazs Scheidler <balazs.scheidler@axoflow.com>
Signed-off-by: Balazs Scheidler <balazs.scheidler@axoflow.com>
Signed-off-by: Balazs Scheidler <balazs.scheidler@axoflow.com>
Signed-off-by: Balazs Scheidler <balazs.scheidler@axoflow.com>
Signed-off-by: Balazs Scheidler <balazs.scheidler@axoflow.com>
The mode field in debugger determines how we respond to trace and
breakpoints and is used by the hook to trigger various debugging
scenarios.

Signed-off-by: Balazs Scheidler <balazs.scheidler@axoflow.com>
Some breakpoints are not interesting once the mode changes, even
though they were submitted by the pipe hook and are waiting to
be resumed.

Let's quickly acknowledge them and don't bother the user.

Signed-off-by: Balazs Scheidler <balazs.scheidler@axoflow.com>
Signed-off-by: Balazs Scheidler <balazs.scheidler@axoflow.com>
Signed-off-by: Balazs Scheidler <balazs.scheidler@axoflow.com>
Also, stop at the prompt immediately, instead of wait for a message.

Signed-off-by: Balazs Scheidler <balazs.scheidler@axoflow.com>
@bazsi bazsi force-pushed the debugger-follow-command branch from 261e471 to b0c2c36 Compare March 20, 2025 07:40
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.

1 participant