Ryan Fleury's banner

Ryan Fleury

@rfleury • 23,352 subscribers

RJF // @dgtlgrove // Making RAD Debugger at @radgametools in @epicgames (opinions my own)

Shorts

This is a huge bang-for-buck improvement you can add to your UIs.

This is a huge bang-for-buck improvement you can add to your UIs.

157,126 görüntüleme

In RADDBG, the "Step Out" command has been upgraded to support block stepping! It now lets you step through blocks, out of loops, or (the traditional behavior) out of function frames.

In RADDBG, the "Step Out" command has been upgraded to support block stepping! It now lets you step through blocks, out of loops, or (the traditional behavior) out of function frames.

27,672 görüntüleme

Almost fully ported the renderer to OpenGL during the last bit of the day This is not for Windows

Almost fully ported the renderer to OpenGL during the last bit of the day This is not for Windows

30,974 görüntüleme

Huge upgrade to loading speeds coming soon, especially with DLL-heavy codebases like UE! The primary reason PDB -> RDI conversion (or PDB parsing in debuggers more generally) is a big bottleneck in startup time is because they must be converted/parsed/loaded _serially_. This may seem surprising, since intuitively it'd seem like they can be converted/parsed/loaded/etc. in parallel. This is not true in the general case due to breakpoints, and how they relate to an API like `LoadLibrary`, and how it translates into debug events. When a debuggee runs `LoadLibrary`, the debugger will receive a debug event informing the debugger that the associated module was loaded. Any time a debug event is sent to the debugger, the debuggee stops running entirely. This is so that the debugger can make decisions about how the debuggee should proceed. For example, if I have a breakpoint on `foo.c:123`, that file name and line number can only be correctly interpreted (meaning resolved into code addresses) using debug information. The debugger only knows about that debug information from the PDB - without it, that file/line combo is meaningless. But importantly, the debugger cannot *resume* the debuggee until it has resolved that breakpoint - otherwise the debuggee may execute code which *would've* hit the breakpoint, *if* it were resolved in time. So, the debugger needs to ensure that all breakpoints are fully resolved before resuming. This is a correctness detail that everyone has to pay for, basically because `LoadLibrary`s are received one-at-a-time. Obviously, if it were instead an API like `LoadLibraries`, then the debugger could prepare all of the debug info in one batch before resuming - but it doesn't know what that batch would be, given just an initial `LoadLibrary`. This is unfortunate, because *generally* you are not debugging the code loading a bunch of DLLs, but the debugger can't really know that. (It is probably a good idea to provide a `raddbg_load_libraries` API at some point, so that we can resolve this issue on the debuggee side). In any case, RADDBG now resolves breakpoints much more quickly by avoiding 99% of debug info conversion work to do a common case of breakpoint resolution - you might call this "breakpoint disqualification". Basically, if a breakpoint is set, and we can quickly determine that that breakpoint's information (file location, expression, condition, etc.) *cannot apply* to some module's debug info - more quickly than doing a *full* PDB -> RDI conversion (which entails a full parse & a bunch of work) - then we can simplify the very common case in DLL-heavy cases: you put a breakpoint on `foo.c:123`, when 99% of the DLLs do not have any line info for that file, so the debugger can resume *knowing* that breakpoint will not resolve within that file. In this demo video, you can see I place a breakpoint that only resolves within the executable's debug info - it does not resolve within any of the 100 DLLs that are loaded serially. Within the `Modules` tab, you can see that as I run the target, most of the debug info is not loaded initially, even though the debuggee is running. That debug info is loading in parallel, as the debugger knows it does not need to wait for that debug info to be prepared for this breakpoint.

Huge upgrade to loading speeds coming soon, especially with DLL-heavy codebases like UE! The primary reason PDB -> RDI conversion (or PDB parsing in debuggers more generally) is a big bottleneck in startup time is because they must be converted/parsed/loaded _serially_. This may seem surprising, since intuitively it'd seem like they can be converted/parsed/loaded/etc. in parallel. This is not true in the general case due to breakpoints, and how they relate to an API like `LoadLibrary`, and how it translates into debug events. When a debuggee runs `LoadLibrary`, the debugger will receive a debug event informing the debugger that the associated module was loaded. Any time a debug event is sent to the debugger, the debuggee stops running entirely. This is so that the debugger can make decisions about how the debuggee should proceed. For example, if I have a breakpoint on `foo.c:123`, that file name and line number can only be correctly interpreted (meaning resolved into code addresses) using debug information. The debugger only knows about that debug information from the PDB - without it, that file/line combo is meaningless. But importantly, the debugger cannot resume the debuggee until it has resolved that breakpoint - otherwise the debuggee may execute code which would've hit the breakpoint, if it were resolved in time. So, the debugger needs to ensure that all breakpoints are fully resolved before resuming. This is a correctness detail that everyone has to pay for, basically because `LoadLibrary`s are received one-at-a-time. Obviously, if it were instead an API like `LoadLibraries`, then the debugger could prepare all of the debug info in one batch before resuming - but it doesn't know what that batch would be, given just an initial `LoadLibrary`. This is unfortunate, because generally you are not debugging the code loading a bunch of DLLs, but the debugger can't really know that. (It is probably a good idea to provide a `raddbg_load_libraries` API at some point, so that we can resolve this issue on the debuggee side). In any case, RADDBG now resolves breakpoints much more quickly by avoiding 99% of debug info conversion work to do a common case of breakpoint resolution - you might call this "breakpoint disqualification". Basically, if a breakpoint is set, and we can quickly determine that that breakpoint's information (file location, expression, condition, etc.) cannot apply to some module's debug info - more quickly than doing a full PDB -> RDI conversion (which entails a full parse & a bunch of work) - then we can simplify the very common case in DLL-heavy cases: you put a breakpoint on `foo.c:123`, when 99% of the DLLs do not have any line info for that file, so the debugger can resume knowing that breakpoint will not resolve within that file. In this demo video, you can see I place a breakpoint that only resolves within the executable's debug info - it does not resolve within any of the 100 DLLs that are loaded serially. Within the `Modules` tab, you can see that as I run the target, most of the debug info is not loaded initially, even though the debuggee is running. That debug info is loading in parallel, as the debugger knows it does not need to wait for that debug info to be prepared for this breakpoint.

17,527 görüntüleme

Videos

Anya Rossi

sweetdream.ai

SweetDream.ai•Sponsored•Livecam

Watch Anya Live

Anya is streaming live right now! Join her private show and enjoy exclusive content.

Exclusive private shows

1.2k viewers online

Private Show

Join now for exclusive access

Free preview available • Premium content

This is not a real company

This is not a real company

4,418,947 görüntüleme • 5 ay önce

Source-inline display of auto watch expressions, computed by determining which addresses are read from / written to by a particular range of instructions, and mapping that back to variables via location info within debug into.

Source-inline display of auto watch expressions, computed by determining which addresses are read from / written to by a particular range of instructions, and mapping that back to variables via location info within debug into.

42,884 görüntüleme • 20 gün önce

Many people have commented on the relatively smaller sizes, faster startup time, better performance, and smoother interactivity of projects like the RAD Debugger or File Pilot. The “secret” is literally just writing things sensibly from scratch. Just stop importing things, and actually solve the problem yourself.

Many people have commented on the relatively smaller sizes, faster startup time, better performance, and smoother interactivity of projects like the RAD Debugger or File Pilot. The “secret” is literally just writing things sensibly from scratch. Just stop importing things, and actually solve the problem yourself.

232,912 görüntüleme • 5 ay önce

More excellence

More excellence

182,604 görüntüleme • 5 ay önce

“native has nothing to offer” No, you’ve just either never bothered to seriously try it, or you just suck.

“native has nothing to offer” No, you’ve just either never bothered to seriously try it, or you just suck.

91,167 görüntüleme • 2 ay önce

Easy to miss if you get lost in the noise in online programming discourse, but straightforward programming in a systems language like C can provide high performance, modern UI, without much hassle.

Easy to miss if you get lost in the noise in online programming discourse, but straightforward programming in a systems language like C can provide high performance, modern UI, without much hassle.

117,229 görüntüleme • 3 ay önce

Left: From-scratch debug build, launching target, and stepping with RADDBG. Right: Launching target & stepping with Visual Studio 2022.

Left: From-scratch debug build, launching target, and stepping with RADDBG. Right: Launching target & stepping with Visual Studio 2022.

620,160 görüntüleme • 2 yıl önce

Someone mentioned to me that they missed a file tree view in the RAD Debugger, so they could easily browse their project folder hierarchy. I then realized I had inadvertently already implemented it in the watch window.

Someone mentioned to me that they missed a file tree view in the RAD Debugger, so they could easily browse their project folder hierarchy. I then realized I had inadvertently already implemented it in the watch window.

30,692 görüntüleme • 1 ay önce

Scope ending annotations

Scope ending annotations

14,164 görüntüleme • 22 gün önce

On the deletion of accounts

On the deletion of accounts

23,648 görüntüleme • 1 ay önce

Getting closer.

Getting closer.

76,195 görüntüleme • 6 ay önce

Palettes should be first class functionality provided by the operating system for any program.

Palettes should be first class functionality provided by the operating system for any program.

85,539 görüntüleme • 9 ay önce

Memory view support for mutation and copy/paste

Memory view support for mutation and copy/paste

20,822 görüntüleme • 1 ay önce

Memory view "peek types" - enter a list of any type expressions, and interpret memory quickly as those types.

Memory view "peek types" - enter a list of any type expressions, and interpret memory quickly as those types.

18,766 görüntüleme • 1 ay önce

I just asked Cursor to remake the Visual Studio debugger but better, look at what it made🤯🤯 Programmers are cooked... 💀

I just asked Cursor to remake the Visual Studio debugger but better, look at what it made🤯🤯 Programmers are cooked... 💀

76,935 görüntüleme • 1 yıl önce

I could only resist implementing cursor trails for so long.

I could only resist implementing cursor trails for so long.

37,205 görüntüleme • 6 ay önce

Why is panel layout such a special-case concept in so many programs?

Why is panel layout such a special-case concept in so many programs?

65,451 görüntüleme • 1 yıl önce

After some excellent work by NIKITA, we have a first pass of DWARF -> RAD debug info conversion up and running on Windows! A big step towards native Linux debugging.

After some excellent work by NIKITA, we have a first pass of DWARF -> RAD debug info conversion up and running on Windows! A big step towards native Linux debugging.

31,579 görüntüleme • 8 ay önce

Why settle for a "command palette", when you could have an "everything palette"?

Why settle for a "command palette", when you could have an "everything palette"?

43,124 görüntüleme • 1 yıl önce

Breakpoint syncing progress

Breakpoint syncing progress

27,166 görüntüleme • 11 ay önce