GliderTrace Examples
Choose a runtime task. Confirm the workspace and runner policy before executing commands or collecting artifacts.
Triage a failing test run
Ask
> Run this test project with GliderTrace. Summarize the first failure and link its available artifacts.
Expected evidence
A stored test session with exit status, failure details, and references to available test artifacts.
Tools: trace_run_tests, trace_get_session
Reproduce a runtime failure locally
Ask
> Run this failing dotnet command. Keep its session available while we inspect the source.
Expected evidence
A session containing command output, normalized events, and artifact references for later inspection.
Tools: trace_run, trace_query_events
Capture a long-running repro
Ask
> Start this application with GliderTrace. Wait for me to reproduce the bug, then stop the session and summarize its evidence.
Expected evidence
A session covering the process lifetime, finalized after trace_stop.
Tools: trace_start, trace_stop, trace_get_session
Import CI artifacts
Ask
> Import these CI test and log artifacts. Export a Markdown summary with artifact references.
Expected evidence
A local session and exported summary that references imported artifacts. Review output before sharing it.
Tools: trace_import_artifacts, trace_export
Compare before and after evidence
Ask
> Compare these two sessions. Identify fixed, new, and persisting failures.
Expected evidence
Fixed, new, and persisting findings between two identified sessions. Keep the commands and environment comparable.
Tools: trace_compare_sessions, trace_export
Inspect counters and hotspots
Ask
> Collect runtime evidence for this slow path. Summarize available counters or CPU hotspots and identify their artifacts.
Expected evidence
Counter or CPU summaries linked to captured evidence. Available collectors and tools determine which results can be produced.
Tools: trace_run, trace_counters, trace_hotspots
Connect exceptions back to code
Ask
> Group exceptions from this session. Correlate their stack frames with C# symbols and identify unresolved frames.
Expected evidence
Exception groups and correlation candidates. Missing source or symbol information can leave frames unresolved.
Tools: trace_exceptions, trace_correlate_code