(riscv)Error executing command 'gdb-set target-async on' [conflicting gdbinit files]

[lapuzen3]

version: 0.27.0
OS: macOS Sequoia 15.3.1
GDB: riscv64-elf-gdb 16.2

I am currently trying to attach my gdb to qemu, emulating riscv64.

My launch.json setting is this:

{
        "type": "gdb",
        "gdbpath": "riscv64-elf-gdb",
        
        "request": "attach",
        "stopAtConnect": true,
        "autorun": [
          "set mi-async on",
          "file ${workspaceFolder}/kernel/kernel",
          "-enable-pretty-printing"
        ],
        "name": "remote debug xv6",
        "executable": "kernel/kernel",
        "target": ":25501",
        "remote": true,
        "cwd": "${workspaceFolder}",
        
        "showDevDebugOutput": true
    }

And due to the debug console, "0x0000000000001000 in ?? ()", I think the attach was successful.
However, after that, gdb terminates and my qemu session terminates also.
Is it due to 'set target-async' command?
How can I fix this?

[GitMensch]

How did you fix this yourself (which is the state of the issue)?

[note: the real error message says you need to interrupt before executing set mi-async on]

[lapuzen3]

I found that there was already set .gdbinit file, and it was like this:

set confirm off
set architecture riscv:rv64
target remote 127.0.0.1:25501
symbol-file kernel/kernel
set disassemble-next-line auto
set riscv use-compressed-breakpoints yes
set mi-async on

So I think that it made collision with the launch.json configuration. When I deleted that line target remote ..., I got right.
I tried to solve this problem literally 10 hours or something. How silly am I!!

[lapuzen3]

[note: the real error message says you need to interrupt before executing set mi-async on]

And I was working with my GPT, he said that was the problem. Therefore I kinda obsessed with that problem. T.T

[GitMensch]

Thanks for the information - so it was a "user issue outside of the extension" (it does not know which gdbinit files are used, the only thing it could do is requesting GDB to not load any gdbinit files - but that will break a bunch of working installations; and one can already add debugger_args: ["-n", "-x"] for that purpose.