guys is there a reason why vscode with gcc on linux (ubuntu) would not show the line where a segmentation fault happened? I'm using gdb as debugger, the program execution halts when it reaces the line that causes the seg fault, but it doesn't highlight it. The call stack says paused on exception, I kinda know why there is that issue: I had linked lists, but the list was not initialized to NULL at first, at a certain point I was trying to use a printf with a string and obviously broke when it reached the garbage data, halting the program. If I run the executable directly I get in the terminal "Segmentation Fault", but vscode halts without the usual notice. There is no reason why it should hide the highlight and banner since anything else like another type of segmentation fault (trying to read a non allocated memory, dividing by zero, ect..) all give out the right banner/highlight
use bt command in gdb
Pavel
Asdew
Daniele
Artöm
vinícius*
V01D
Pablo
Pavel
Dima
Vlad
Yosef