I used this trick when doing my bomblab assignment. Helps so freaking much. A big tip here is also that control+L refreshes the TUI, as it often gets weirdly "corrupted" and needs often refreshing.
I always respected my professors at university and learned many things from them, but I think I have learned even more from you. Thank you professor and please keep on your valuable online courses.
Hi Jacob, can you do tutorial, maybe share some tweaks on how to better understand other people's code, especially when it's a big project with a lot of .c and .h files? Thanks.
I have this "m68k-elf-gdb.exe" gdb client wich i use to debug 68k assembly, but it does not support tui....i've been trying to recompile it whit added support with no luck, any idea on how to enable tui in this version???
I see that you can also see the values stored in the registers live. Is it possible to have all 3 shown at once? C code, Assembly, and register values?
Hi, tnx 4 ur awesome tutorials. Can u make a tutorial on how to build an ISO imagine of a Linux kernel from Linux source code that can actually be used in virtualbox
@@JacobSorber thanks for this again. just passed my exam with highest marks and i used gdb to debug. define hook-stop helped me speed things up so much!
Thanks, Jannis. Yes, you need curses support for this to work. Also, if you don't want to cycle through the layouts, and you know which one you want, just type "layout split" to get the split layout, or "layout src" for just the source and command views.
Today's terminal debuggers (gdb, lldb) definitely aren't perfect, but after using dozens of different debugging tools, it's amazing how a quick gdb session (with a reasonably good .gdbinit file) is still often the fastest option for me. There's definitely a learning curve.
Thank You for demonstrating the TUI in GDB. This is going to be Helpful.
You're welcome. Glad I could help.
I used this trick when doing my bomblab assignment. Helps so freaking much.
A big tip here is also that control+L refreshes the TUI, as it often gets weirdly "corrupted" and needs often refreshing.
The command "ref" does the same
Nice video and happy new year to all fellow C programmers!
Happy new year!
Cool. I didn't know about that. Been coding for 30 years and still learning. That's why I like your channel.
Me too. Glad I could help.
Not having known about this before, you have just revolutionized my debugging experience!
This is amazing! Had no idea this was a feature and I've been painfully using GDB this entire semester....
Instead of "b main" & "r" you could just do "start".
Also, instead of "layout next" use "layout src" (or whatever layout name you want).
I always respected my professors at university and learned many things from them, but I think I have learned even more from you. Thank you professor and please keep on your valuable online courses.
This is a godsend, thank you!
This is so good! Thank you so much!
thank you for gdb demo.
wow. where have you been all my life ...
You are a hero !
Hi Jacob, can you do tutorial, maybe share some tweaks on how to better understand other people's code, especially when it's a big project with a lot of .c and .h files? Thanks.
I would like that to!
There are extensions to gdb like pwndbg or peda that make it much more friendly.
i was aware of tui, but not of changing layouts.
and the nexti,stepi could be huge!
Yeah, I don't use them ever day, but when they're useful...they're REALLY useful.
I think it would be great if you made a discord server. Just for people to share and learn from others and it would be easier to help people.
Seems to be awesome
its gdb time
I usually just press ctrl-x-a
I have this "m68k-elf-gdb.exe" gdb client wich i use to debug 68k assembly, but it does not support tui....i've been trying to recompile it whit added support with no luck, any idea on how to enable tui in this version???
Short AND helpful. :)
I see that you can also see the values stored in the registers live. Is it possible to have all 3 shown at once? C code, Assembly, and register values?
Would you please make a video about Math in embedded systems and btw very helpful videos keep going
BTW, GDB in MacOS Venura Gives error , some odd libraries permissions error for setting break points
Does this command works in putty session? What to do if it doesn't?
Fantastic!
Would be nice to have some tool to visualize and compare big arrays on GDB
Cannot enable the TUI: error opening terminal [TERM=xterm-256color]
do you know if there's a layout gdb for java programs?
Hi, tnx 4 ur awesome tutorials. Can u make a tutorial on how to build an ISO imagine of a Linux kernel from Linux source code that can actually be used in virtualbox
thanks a lot!!!!
Can you do a tutorial about Radare2?
Yeah, probably. I'll add it to my topic list and see what I can do down the road. Thanks.
is there a way for me to display stack at every step? or have a window dedicated to stack? instead of typing bt full every step. thanks for the video!
Of course. 😀type "define hook-stop". Then type in "bt", then "end". Now, every time your program stops, gdb will run "bt" for you.
@@JacobSorber thank you very much!!!
@@JacobSorber thanks for this again. just passed my exam with highest marks and i used gdb to debug. define hook-stop helped me speed things up so much!
It is better to use GDB inside EMACS with the full 6 viewports.
Hi Jacob. How did you split these two views: C and Assembler ?
At 2:19 you see that with "layout next" you can find the layout you are looking for.
depending on the terminal, you might not have curses support, specially Windows Comand line doesn't have curses support as far as I know.
Thanks, Jannis. Yes, you need curses support for this to work. Also, if you don't want to cycle through the layouts, and you know which one you want, just type "layout split" to get the split layout, or "layout src" for just the source and command views.
don't apologize that it was a short video, everyone who clicks on the video sees it before they click ;)
Really not much information in this video but just introducing a bit the feature
754 Gloria Rapid
1:36 TUI
Hegmann Well
Denesik Streets
bruuhh arm-aebi-none-gdb 2020 doesnt support tui.
VIM, GCC, GDB
The rest is unnecessary :)
You forgot MAN
Linux has still in olden days debugging techniques, this is seem to be tedious debugging as well less devolper friendly
Today's terminal debuggers (gdb, lldb) definitely aren't perfect, but after using dozens of different debugging tools, it's amazing how a quick gdb session (with a reasonably good .gdbinit file) is still often the fastest option for me. There's definitely a learning curve.