I am currently trying to debug a C program in Visual Studio Code using gdb (on Windows) but when I start it in the integrated terminal, the text becomes unreadable after a few lines of code had been executed. Some goes to the right side of the terminal, other doesn’t even print. However, when I set “externalConsole” to true and use that instead, everything works. The thing is that using the external console is not quite convenient for me. So far I have tried restarting VS Code and setting "externalConsole" to true. Any ideas on how to fix this?

I’m trying to use GDB/GEF for the first time, but whenever I try to run the binary after setting a breakpoint (tried at both main and another random address) I get:

I’m debugging a zig binary where there is a union with the following fields:

I wrote a while loop in GDB to print all threads’ backtrace except for thread 306 and 310.

I want to better understand sigaction and I have reached this instruction using gdb.

I’m learn aosp6.0.0_r1 , now i want to lean binder , I want to debug android_util_binder.cpp .
but I don’t know how to start the debug .

When I stop gdb I automatically get info. For example, consider the following, where I continue the execution of a program and then I stop it:

GDB -break-commands not work when attach a running process