From GDB 14 on, tracepoints seem to be working again (they have been broken since v9 apparently). What I have not succeeded in is usung tsave and then loading with remote tfile. Traces appear always empty.
Oh, it does make sense to name the bad guy after an OS. You are probably too young to understand this. When I was as student I came into contact with IBM's CMS running on an Amdahl Mainframe. It was already heavily out-dated by then but still kept alive for running legacy software. The user experience was so terrible that I can fully understand the joke. I had to debug some old Fortran programs for a research institute and it was a good thing that the IBM 3278 terminal came with a durable steel case. Not only I would regularly band on it. BTW - great talk! Thanks!
![ไลฟ์สุ่ม iPhone 295 บาท... โกงมั้ย?[ โกงมั้ยครับ ep.97 ] | DOM](http://i.ytimg.com/vi/gdstHEE4UUE/mqdefault.jpg)
This is the single best debugging video I have ever watched, ever.
Impossible. How can You say it. I can't get past first few words because of the accent :/
Super fan here! Thanks a ton for this great 👍 work!😍
It would be cool if you make a video series about creating a Desktop Enviroment or window Manager with X11
well-done!
Excellent share :D Thank you very much
From GDB 14 on, tracepoints seem to be working again (they have been broken since v9 apparently). What I have not succeeded in is usung tsave and then loading with remote tfile. Traces appear always empty.
Awesome
At least I know now that "tracing" is also not working for others :)
I am using 12.1 version for both gdb and gdbsever. Tracepoints not working for these version. Any fix or WAR ?
Oh, it does make sense to name the bad guy after an OS. You are probably too young to understand this. When I was as student I came into contact with IBM's CMS running on an Amdahl Mainframe. It was already heavily out-dated by then but still kept alive for running legacy software.
The user experience was so terrible that I can fully understand the joke. I had to debug some old Fortran programs for a research institute and it was a good thing that the IBM 3278 terminal came with a durable steel case. Not only I would regularly band on it.
BTW - great talk! Thanks!
for stripping the debug info from the exec. I think you are looking for --gsplit-dwarf argument for gcc.
thank you.
Thanks Sir! For Great gdbTips..
Curious about "gdb multi arc"
You can jump into a gdb session with a coredump loaded with coredumpctl debug. No need for the extra step of dumping the coredump.
wouldn't you just use the linux ftrace command for tracing ?
That would be for tracing OS calls only. A trace point in gdb is for any line of code in your program.
😀