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: prompts/agent/crash_analyzer-priming.txt
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
-
Given the following crash report, fuzz driver code and relevant project function code, analyze the cause of the crash using LLDB tool step by step.
2
-
First, make a conclusion, only answer “Crash is caused by bug in fuzz driver” or “Crash is caused by bug in project”. Second, offer succinct and to-the-point analyses and suggestions.
1
+
Given the following crash report, fuzz driver code and relevant project function code, analyze the cause of the crash using GDB tool step by step.
2
+
First, make a conclusion, ONLY ANSWER "False" if the crash is caused by bug in fuzz driver OR ONLY ANSWER "True" if the crash is caused by bug in project. Second, offer succinct and to-the-point analyses and suggestions.
3
3
4
4
Below is crash report:
5
5
<log>
@@ -16,4 +16,4 @@ Below is relevant project function code:
16
16
{PROJECT_FUNCTION_CODE}
17
17
</code>
18
18
19
-
To help analyze the root cause behind the runtime crash, you can leverage LLDB tool and BASH tool to obtain information.
19
+
To help analyze the root cause behind the runtime crash, you can leverage GDB tool and BASH tool to obtain information.
Given the following crash report, fuzz driver code and relevant project function code, analyze the cause of the crash.
2
2
3
-
First, make a conclusion, only answer “Crash is caused by bug in fuzz driver” or “Crash is caused by bug in project”. Second, offer succinct and to-the-point analyses and suggestions.
3
+
First, make a conclusion, ONLY ANSWER "False" if the crash is caused by bug in fuzz driver OR ONLY ANSWER "True" if the crash is caused by bug in project. Second, offer succinct and to-the-point analyses and suggestions.
You can leverage GDB by iteractively sending me a GDB command, and I will provide you with the output of the command. The path of fuzz driver binary is '/out/{TARGET_NAME}'. The testcase that triggers runtime crash is stored at '{AFTIFACT_PATH}'.
4
+
5
+
<interaction protocols>
6
+
1. I have executed 'gdb /out/{TARGET_NAME}'. You are now in GDB session, NOT in shell session. DO NOT run 'gdb /out/{TARGET_NAME}' again! DO NOT run shell commands!
7
+
2. Strictly ONE GDB command at a time!
8
+
3. Each message you send should first explain the reason why you want to run the command wrapped by <reason></reason>, then provide the command to run wrapped in <gdb></gdb> in this format:
9
+
<reason>
10
+
Reasons here.
11
+
</reason>
12
+
<gdb>
13
+
One gdb command here.
14
+
</gdb>
15
+
4. Each reponse I send will repeat the command you sent wrapped in <gdb command></gdb command> for you to double-check, followed by the command standard output wrapped in <gdb output></gdb output> and stderr wrapped in <stderr></stderr> in this format:
16
+
<gdb command>
17
+
The command I executed, copied from the command you sent.
18
+
</gdb command>
19
+
<gdb output>
20
+
The standard output of the command.
21
+
</gdb output>
22
+
<stderr>
23
+
The standard error of the command.
24
+
</stderr>
25
+
5. The final goal is to answer questions about runtime crash, executed fuzz driver and project under test: a) ‘False’(if the crash is caused by bug in fuzz driver) or ‘True'(if the crash is caused by bug in project)? b) If the crash is caused by bug in fuzz driver, provide analyses, and are there any suggestions for modifying the fuzz driver? c) If the crash is caused by bug in project, provide analyses, and are there any suggestions for patching the project?
26
+
6. If you have a conclusion on above questions, output the conclusion wrapped by <conclusion></conclusion> followed by the analysis and suggestion wrapped in <analysis and suggestion></analysis and suggestion>:
27
+
<conclusion>
28
+
‘False’ or ‘True’
29
+
</conclusion>
30
+
<analysis and suggestion>
31
+
Analysis and suggestion
32
+
</analysis and suggestion>
33
+
</interaction protocols>
34
+
35
+
<general rules>
36
+
1. DO NOT wrap code snippets with ```, using the XML-style tags above will suffice.
0 commit comments