CppCon 2015: Greg Law ' Give me 15 minutes & I'll change your view of GDB'

preview_player
Показать описание


Lightning Talk


*-----*
*-----*
Рекомендации по теме
Комментарии
Автор

Wow. I've been using GDB for years and I never knew it could do all of this.

redpillcommando
Автор

For so many years printf for me was more useful than gdb. This talk has changed everything.

xvoidee
Автор

Debugging is incredibly useful, even when a lot of people insist that print statements are sufficient. This talk inspires me to not be too dependent on CLion for debugging.

andrerong
Автор

When he's talking about in TUI being stuck in the source window you can switch windows using ctrl+o, this will allow up/down arrows again in the command window.

reductor_
Автор

Finally a YouTube title that delivers!

dustinmorrison
Автор

This was good, for some of us who cannot use IDE for coding and debugging. Wasn't aware of recording and reverse-continue. Thanks.

prasadjoshi
Автор

I didn't know GDB was that powerful. Thankfully I joined one of his sharing about Undo (His company's product for time travelling debug), so I remember his name. What a gems here! Thanks a lot for the content, and please keep up the good work.

haiphamle
Автор

This quite annoying to follow when the first column is cut off by the screen-recording tool.

pcfreak
Автор

For me, who is used to Java and it's debugging via UI, c++ debugging and using gdb for that feels almost magical and I love it

harishkumar-jxxw
Автор

We had a follow-up advertised, but on the channel, there's nothing after this about GDB until next year.

zoltantorok
Автор

Excellent Powerful presentation. Thanks.

sambell
Автор

When you discover all the power you had until now but didn't know that you can use !!!

petretrusca
Автор

Ctrl-p / Ctrl-n are common readline bindings.

derysf
Автор

You just saved lives with your 15 mins. Thanks, it was awesome.
Now I feel that I was wasting time on GUI based debuggers!
Still... for huge projects, GUI based debuggers help better.

jp
Автор

these tools are amazing. Its like there is a new debugging tool i never heard of inside gdb!

james
Автор

2:29 "CTRL + x, a" very nice trick, I like this video.

deltakid
Автор

it seems those key combinations are come from emacs (at least emacs style), great for emacser xD

i use gdb in emacs so im not worrying about the UI, but its really cool that u tells how to findout those segmentation fault bug and how to locate it, great video

tsukuyomu
Автор

Did the emacs commands get incorporated into gdb proper? I often used emacs and used these commands to put a line marker in code and split window into 2 for the gdb CL. This is cool!

vicmulyk
Автор

Under Ubuntu 18.04, core dumped file didn't get written into the current directory. The simplest and fastest way to resolve this is to `ulimit -c unlimited` then run the binary file again, the core file will be there.

haxpor
Автор

I just tried using the record command with a real application. The recording took so much CPU the inferior process was running many times slower. It ran for a couple minutes and I never saw the startup messages. It is a TCP server and the client timed out trying to connect. I have no idea how many instructions per seconds were actually being executed. I tried using hardware trace support but my Intel CPU does not support it. The hardware is a single board computer with 4th Gen Intel Core. Oh there are a dozen threads running.

j.r.heisey