Today we're announcing Claude Code plugins!
https://t.co/WD2TfN8d3d
It's the first major feature in Claude Code that I've gotten the opportunity to lead, and I'm really excited to see how everyone uses it! 🧵1/4
Tired of chasing values across processes? 😩
UDB & Live Recorder let you:
🔎 Record & replay multi-process execution
🔄 Track IPC flow across C & C++ apps
⚡ Find & fix bugs faster than ever
Watch Magne Hov’s guide now! 🎥
https://t.co/ognrjIn0J5
#Cprogramming#Testing
The latest TTD release includes some pretty cool changes; you can now 'break on registers' (!tt br) & navigate to the next module boundary (!tt bm) and more! 🔥
https://t.co/gfoNPtzyRr
In light of the recent news about DeepSeek AI, check out our new YouTube Video!
How DeepSeek AI Works Under The Hood - Watch Replayed Program Execution with Time Travel Debugging
https://t.co/seB1afZ9RU
#Coding#Openai#Programming
Check out our new C & C++ debugging tutorial using the Undo Visual Studio Code Extension!
How To Debug C++ & C in VS Code - Debugging Race Conditions
https://t.co/7Nk9v77b2S
#Cplusplus#Cpp#Vscode
Guilty!: https://t.co/EpsJCCWsHl
- Spends so much time talking about time travel debugging, [...] dreams in reverse chronological order
- [...] used GDB more times than most people have used their smartphone
This is the American Radiator Building, a 101 year old black and gold skyscraper that's half Gothic, half Art Deco.
It's famous, but not as famous as it should be — so here's a brief history of one of the world's coolest skyscrapers...
@culturaltutor The instant I saw the American Radiator building it became my favourite skyscraper in New York. I also go looking for it in Open World video games but am generally disappointed :-(
@Glaucous_Noise@ID_AA_Carmack Huh, I actually wouldn't have expected a substantial slowdown from the debugger on one of those - do you have any idea where the performance is lost? Is it also an unoptimised build?
@Glaucous_Noise@ID_AA_Carmack Ah, what language? Compiled language debuggers generally get pretty close to zero overhead because of how they're implemented - but other runtimes choose a different tradeoff. Ideally all languages would have a zero overhead debugger but it does create some challenges.
@Andrath1975@ID_AA_Carmack The annoying thing about "optimized out" is that it makes it harder to reason about some parts of the program - I think compilers don't always generate the quality of debug information to reason well about this stuff (but being able to inspect it at all is an improvement on not!)
@eeuoss@meow464_@ID_AA_Carmack Over time I've come to quite like the GDB command line interface - it's not perfect but actually the core command set is quite small and fairly consistent. But your point about building with -g is interesting - it's not even just the debugger, it's the whole ecosystem.