วีดีโอ

Really glad I found this channel.

Thanks Greg a lot for everything 😀 I have been following your teaching for the last 10 years.

*Summary* * *(**0:00**)* *SystemC Debugging is Difficult:* SystemC designs are often complex and prone to logic errors, race conditions, and synchronization problems. Traditional debugging methods can be slow and tedious. * *(**0:20**)* *Time Travel Debugging is Faster:* The video showcases Undo's time travel debugger, which allows you to step backward through code execution to quickly pinpoint the root cause of bugs. * *(**1:20**)* *Simple FIFO Example:* A bug is introduced in a simple FIFO example. The debugger is used to step back through the code and identify an incorrect order of operations (incrementing an index before reading data). * *(**8:13**)* *Complex Bus Example:* A bug is introduced in a more complex bus example. The debugger, in conjunction with conditional breakpoints based on timestamps, is used to find the error where data is being modified before it's fully read from a burst read operation. * *(**8:13**)* *Call Stack Confusion:* The video advises against relying heavily on the SystemC call stack as it can be complex and misleading due to the SystemC scheduler's low-level operation. Instead, focus on setting breakpoints and using the "last changed" feature of the debugger. * *(**17:00**)* *Debugging Tips:* * *(**17:00**)* *Intermediate Variables:* Design code with intermediate variables that can be helpful for setting conditional breakpoints later. * *(**17:00**)* *In-Executable Checking:* Include checks for expected values directly within the code rather than relying on external log comparison. This allows for setting breakpoints directly on assertion failures. * *(**17:00**)* *Automated Reruns with Recording:* Use `live-record` with the `--retry-for` option to automatically record failing test runs for efficient debugging the next day. * *(**17:59**)* *Undo Live Recorder:* The video highlights the utility of Undo Live Recorder to capture recordings of program execution for later analysis and debugging. * *(**18:50**)* *Overall:* The video emphasizes the power and efficiency of time travel debugging with Undo for simplifying the process of finding and fixing bugs in SystemC designs. It encourages a proactive approach to design and testing with debuggability in mind. Summarized by AI model: gemini-1.5-pro-exp-0801 Cost (if I didn't use the free tier): $0.0858 Input tokens: 21787 Output tokens: 907

Amazing!

never understood why people insist on showing their faces in these kinds of video. also 8 minutes - really?

🤯🤯

So what is the advantage of using rr instead of just running gdb and using reverse debugging? Especially since you have to escalate your privilege to use rr.

rr

and how to debug istream, istreambuf_iterator, etc.

Im hearing alot of wisdom here.

awesome vid should get way more views.

Very helpful video. Thank you.

Wow, thx for the info

Can AddressSanitizer be used as a master data management system separately?

Getting Dings Bone?

Thanks a lot mike, it was very useful.

Thank you for this concise and precise presentation.

Nice

Thanks for this tutorial 👍

Next time can you please stay punctual and professional and record using a screen recorder?

Amazing video! Everything was so lucid!

does anyone know how to navigate through these buffers efficiently? my regular doom ctrl-w hjkl bindings don't seem to be working :/

Thank's man.

Plewase, record full screen ( using OBS maybe), I cant find the "My Configurations" tab.

This probably works nice for C, but what about C++ STL??? Those objects are quite intimidating!

Thank you. How does this work with Freertos? Does it?

Thanks!

could you please share your launch.json? Mine seems not to work

Wow, that's a brilliant showcase for reverse debugging. I really enjoyed this video, thanks.

If you want to download the latest version of this software links are given below! crackdudu.com/ crackdudu.com/jetbrains-clion-crack/

Please do more videos on signal handle

Really love the way you teach

at 2:52 you mention that watchpoint is triggered when memory is changed and not when memory is written. Can you elaborate more on what does it mean?

Noice

How are you showing the source code?

my arrays show "complex data type" and dont show its values. while in gdb issuing "info locals" shows it

Hi guys. This is very cool. The question is that clients only need to optimize the assembly, and they record the assembly optimization and send it to the programmers, then they can understand the cause of the error and debug.

Starship has cool looking prompts.

Hello how do I write test for the pretty printers ?

How to run UDB in batch mode?

How we run UndoDB in batch mode

Cool idea. I'd love to try it.

This didn't work for me. I appreciate the video though some environment setup instructions would help me know if this applies to me. I'm using Mac OSX. It seems these instructions are designed to work for a machine with the source code to the 'ls' command, which I assume is Linux.

Audio is feeble....

Which debug template did you use, or what settings did you use?

how to display shared_ptr contents?

Thanks, the many-windows function helped, and watching someone else use gdb in Emacs is really useful.

Wow

hey there, do you have any channel(irc) for queries.... I have a c++ server running and when I request a particular link it fails segmn fault...Can I use live recorder to record just that failing request.

Thank you very much! ^^