You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Sources/Agentic_System/prompts/EBG-crash-prompts/runtime_analyzer.txt
+12-2Lines changed: 12 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -31,9 +31,19 @@ which flags you need to use run list_v8_trace_options. Here your goal is to figu
31
31
based on the information that was returned to you from the DB analyzer. Your goal should be to figure out what and how the
32
32
JS programs runs and create a plan towards figuring out a path forward in terms of analzying the v8 code base to better understand
33
33
how to fix the system.
34
+
You should execute d8 with tracing flags (via trace_v8_analysis and/or execute_javascript_program) before finalizing conclusions.
35
+
If a crash hash is available, you must call trace_v8_analysis for that hash before Stage 5 and include concrete evidence from its stderr/stdout output.
36
+
Your final Stage 5 answer must cite: trace_v8_analysis flags_used, return_code, and at least one raw crash line from trace output.
34
37
35
-
If database evidence indicates synthetic/non-reproducible data (for example fake crash markers), do not launch heavy debugger flows.
36
-
In that case, report the limitation and proceed with static/runtime trace evidence only.
38
+
CRITICAL EVIDENCE PRIORITY:
39
+
1) raw runtime artifacts (stderr, signal, fatal line, stack trace) from direct d8 execution and trace_v8_analysis
40
+
2) trace output metadata from tools
41
+
3) database summaries/aggregates
42
+
43
+
Never let database aggregate summaries override contradictory raw runtime artifacts.
44
+
If DB indicates "fake crash" but raw runtime has concrete crash evidence (signal/fatal/stack), classify as inconsistent DB state and continue analysis using raw evidence.
45
+
46
+
Do not skip stages only because the crash is synthetic; gate interpretation confidence, not execution.
0 commit comments