Загрузка видео...

Не удалось загрузить видео

На главную

Excited about a new debug feature in Visual Studio Code for all languages: Triggered Breakpoints! Triggered breakpoints are activated only when another breakpoint gets hit. Really useful when looking for that one bug in code with lots of events or loops:

ConnorPeet's profile picture

Connor Peet

1,531 subscribers

33,190 просмотров • 2 лет назад •via X (Twitter)

Наука и технологии
LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

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.
0:18

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.

Ryan Fleury

17,527 просмотров • 11 месяцев назад

Introducing Customizable Responsive Breakpoints for Divi 5. 🥳 Divi 5 now comes with seven pre-defined breakpoints that cover every type of device, and you can customize the width of each breakpoint to control your design at every size. 👇
0:20

Introducing Customizable Responsive Breakpoints for Divi 5. 🥳 Divi 5 now comes with seven pre-defined breakpoints that cover every type of device, and you can customize the width of each breakpoint to control your design at every size. 👇

Elegant Themes

3,655,477 просмотров • 1 год назад

GitHub Copilot Chat gets an update with the new Interactive Code Assistant View in Visual Studio, Quick Chat in Visual Studio Code, and an expanded context window to help provide better suggestions! 🥳
0:16

GitHub Copilot Chat gets an update with the new Interactive Code Assistant View in Visual Studio, Quick Chat in Visual Studio Code, and an expanded context window to help provide better suggestions! 🥳

GitHub

225,221 просмотров • 2 лет назад

🚀 A new Visual Studio Code weekly release is here! One of our favorite features is integrated browser debugging, which lets you debug your web app end-to-end without leaving the editor.
0:14

🚀 A new Visual Studio Code weekly release is here! One of our favorite features is integrated browser debugging, which lets you debug your web app end-to-end without leaving the editor.

Visual Studio Code

137,062 просмотров • 2 месяцев назад

🚨Beta alert!! From a Figma link to React in Visual Studio Code Visual Studio Code >Extension here:
0:18

🚨Beta alert!! From a Figma link to React in Visual Studio Code Visual Studio Code >Extension here:

Anima

4,914,162 просмотров • 2 лет назад

With GitHub Copilot for Azure in Visual Studio Code, developing for Azure has never been easier! From asking questions about @azure services to deploying solutions with Azure AI features, try it out now:
0:15

With GitHub Copilot for Azure in Visual Studio Code, developing for Azure has never been easier! From asking questions about @azure services to deploying solutions with Azure AI features, try it out now:

Visual Studio Code

53,877 просмотров • 1 год назад

In the latest release of the Ruby LSP extension for Visual Studio Code, we added a dependencies view showing all gems in the application. We want to add more integrations with Bundler for managing dependencies, like adding, updating and removing gems. What do you think would be useful?
0:14

In the latest release of the Ruby LSP extension for Visual Studio Code, we added a dependencies view showing all gems in the application. We want to add more integrations with Bundler for managing dependencies, like adding, updating and removing gems. What do you think would be useful?

Vinicius Stock

23,549 просмотров • 2 лет назад

Coming soon to a pre-release channel in Visual Studio Code, test coverage support for C# #dotnet
0:13

Coming soon to a pre-release channel in Visual Studio Code, test coverage support for C# #dotnet

Tim

15,735 просмотров • 1 год назад

💾 in the next version of Visual Studio Code, auto save can be configured as a workspace setting and per language. 🙌 A new setting allows to auto save only when there are no errors in the file. 👌 try this out today from our insiders channel at
0:19

💾 in the next version of Visual Studio Code, auto save can be configured as a workspace setting and per language. 🙌 A new setting allows to auto save only when there are no errors in the file. 👌 try this out today from our insiders channel at

Benjamin Pasero

29,001 просмотров • 2 лет назад

You might already know that you can drag editors into their own floating window in Visual Studio Code. But did you know that this works for the terminal too?
0:16

You might already know that you can drag editors into their own floating window in Visual Studio Code. But did you know that this works for the terminal too?

Visual Studio Code

77,106 просмотров • 1 год назад

You can now route each request to the "fastest" ⚡ or "cheapest" 💸 provider with Hugging Face Inference Providers in Copilot Chat on Visual Studio Code!🤗 For each model, you can explicitly choose "cheapest" when price matters - or "fastest" when throughput is the priority. thanks to Simon Brandeis for shipping this!
0:18

You can now route each request to the "fastest" ⚡ or "cheapest" 💸 provider with Hugging Face Inference Providers in Copilot Chat on Visual Studio Code!🤗 For each model, you can explicitly choose "cheapest" when price matters - or "fastest" when throughput is the priority. thanks to Simon Brandeis for shipping this!

célina

33,220 просмотров • 7 месяцев назад

Searching for files in large projects has never been easier 🚀 Check out the real-time search results for the #vscode project, which has thousands of files (and yes, we use Visual Studio Code to write Visual Studio Code). You can easily switch between fuzzy matching and continuous matching too!
0:16

Searching for files in large projects has never been easier 🚀 Check out the real-time search results for the #vscode project, which has thousands of files (and yes, we use Visual Studio Code to write Visual Studio Code). You can easily switch between fuzzy matching and continuous matching too!

Visual Studio Code

241,649 просмотров • 1 год назад

The terminal feature you've been looking for?
0:12

The terminal feature you've been looking for?

Visual Studio Code

348,946 просмотров • 2 лет назад

🚀 We just released Zed v0.197! If the Debug Adapter for your language supports it, you can now configure breakpoints such that the debugger only stops on them based on variable access patterns: Read, Write, Read & Write. This is super useful for tracking down unexpected data changes to your application state.
0:18

🚀 We just released Zed v0.197! If the Debug Adapter for your language supports it, you can now configure breakpoints such that the debugger only stops on them based on variable access patterns: Read, Write, Read & Write. This is super useful for tracking down unexpected data changes to your application state.

Zed

14,667 просмотров • 10 месяцев назад

Experimenting with tldraw, xyflow · React Flow · Svelte Flow & Mermaid JS as visual ways to interact with a code base for interactive modern code review. Claude & Codex can generate so much code so quickly that we are going to need new ways to review and understand their work. Markdown documents, ERDs, tree-maps, flow-charts, systems architecture diagrams, process maps. These could be the new lingua franca of a higher level abstraction of software development. What you're seeing below is a visualisation of the database structure of a Laravel app, automatically generated in a visual code review tool to help with the review of a new feature.
0:15

Experimenting with tldraw, xyflow · React Flow · Svelte Flow & Mermaid JS as visual ways to interact with a code base for interactive modern code review. Claude & Codex can generate so much code so quickly that we are going to need new ways to review and understand their work. Markdown documents, ERDs, tree-maps, flow-charts, systems architecture diagrams, process maps. These could be the new lingua franca of a higher level abstraction of software development. What you're seeing below is a visualisation of the database structure of a Laravel app, automatically generated in a visual code review tool to help with the review of a new feature.

Peter Thomson

27,029 просмотров • 4 месяцев назад

The Visual Studio Code team is shipping fast, with new updates landing every week. Here are a few recent highlights
0:18

The Visual Studio Code team is shipping fast, with new updates landing every week. Here are a few recent highlights

Microsoft Developer

48,181 просмотров • 1 месяц назад

🌩️New channel ability triggered when targets move (in co-op)
0:10

🌩️New channel ability triggered when targets move (in co-op)

Duel Corp 🎮

50,792 просмотров • 8 месяцев назад

🐍 Python devs: who likes generating documentation? Probably not you. Luckily it just got more convenient in Visual Studio Code with Pylance's docstrings template generation feature! This can be enabled with the python.analysis.supportDocstringTemplate setting ⚙️
0:19

🐍 Python devs: who likes generating documentation? Probably not you. Luckily it just got more convenient in Visual Studio Code with Pylance's docstrings template generation feature! This can be enabled with the python.analysis.supportDocstringTemplate setting ⚙️

Visual Studio Code

52,764 просмотров • 1 год назад

On a ✨NEW #AzureFriday with Scott Hanselman 🌮🌮 – Rong Zhang and Tatsat Mishra are back with updates to the #AKS Tools extension in Visual Studio Code #K8s
0:16

On a ✨NEW #AzureFriday with Scott Hanselman 🌮🌮 – Rong Zhang and Tatsat Mishra are back with updates to the #AKS Tools extension in Visual Studio Code #K8s

Azure Friday ⛅📺

12,334 просмотров • 2 лет назад