Description:
On commit 4bb4897efbe257d3ee06916e0713bfed150a079c. Only occurs in GDB, only when LLM tries to call a GDB function using "debug". After the first followup query, ChatDBG appears to get stuck waiting on input. It can still take and execute commands, but does not print the query cost or (ChatDBG gdb) prefix until the user quits. Before quitting, all messages print at once.
Replication:
gdb ./a.out
run
why Try using print
why Try using print
<Further commands can be given, but the above is enough to trigger the bug>
Description: On commit 4bb4897efbe257d3ee06916e0713bfed150a079c. Only occurs in GDB, only when LLM tries to call a GDB function using "debug". After the first followup query, ChatDBG appears to get stuck waiting on input. It can still take and execute commands, but does not print the query cost or (ChatDBG gdb) prefix until the user quits. Before quitting, all messages print at once.
Replication: