Closed wilmer-suarez closed 1 year ago
I think what happened is that the response to your input was an undefined command in GDB?
Generally, this issue happens when the GPT model hallucinates commands, which happens occasionally (in my testing, it's quite rare). There is unfortunately no way of stopping that from happening.
This happens during GDBs initialization actually, before inputting any command:
This is what's in my .gdbinit
file:
After doing some research, I think the issue may have something to do with your arm-none-eabi-gdb
not being compiled with python support. There should not be an issue with the script.
Yeah, that seems to be the case. If I can figure out a way to get past that I will post here. Thank you
I came across this, you might find it helpful. https://gist.github.com/JayKickliter/8004bafaf3d365dc8fe23843fae15c67
Let me know if it works.
Any way around this? I'm running
arm-none-eabi-gdb