Skip to content

Commit e733d0b

Browse files
author
William Xie
authored
Update debug-live-azure-applications.md
1 parent 8d007b6 commit e733d0b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/debugger/debug-live-azure-applications.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -154,13 +154,13 @@ When the Snapshot Debugger captures a snapshot of your app, it is forking the ap
154154
When you have multiple instances of your app, snappoints get applied to every single instance. Only the first snappoint to hit with the condtions specified will create a snapshot. If you have multiple snappoints, subsequent snapshots will come from the same instance that created the first snapshot. Logpoints sent to the output window will only show messages from one instance, while logpoints sent to application logs will send messages from every instance.
155155

156156
#### How does the Snapshot Debugger load symbols?
157-
The Snapshot Debugger requires you to have the correct symbols corresponding to your application either locally or deployed to your Azure App Service. The Snapshot Debugger will automatically download symbols from your Azure App Service. As of Visual Studio 2017 (version 15.2), deploying to Azure App Service will also deploy your app's symbols.
157+
The Snapshot Debugger requires you to have the correct symbols corresponding to your application either locally or deployed to your Azure App Service (we don't currently support embedded PDBs). The Snapshot Debugger will automatically download symbols from your Azure App Service. As of Visual Studio 2017 (version 15.2), deploying to Azure App Service will also deploy your app's symbols.
158158

159159
#### Does the Snapshot Debugger work against release builds of my application?
160-
Yes - the Snapshot Debugger is intended to work against release builds. When a snappoint is placed in a function, we temporarily recompile that function back to a debug version, making it more debuggable. When you stop the Snapshot Debugger, functions are returned to their release build.
160+
Yes - the Snapshot Debugger is intended to work against release builds. When a snappoint is placed in a function, we temporarily recompile that function back to a debug version and making it debuggable. When you stop the Snapshot Debugger, the functions are returned to their release build.
161161

162162
#### Can logpoints cause side effects in my production application?
163-
No - any log messages you add to your app are virtually evaluated. They cannot cause any side effects in your application. However, some native properties may not be accessible with logpoints.
163+
No - any log messages you add to your app are evaluated virtually. They cannot cause any side effects in your application. However, some native properties may not be accessible with logpoints.
164164

165165
#### Does the Snapshot Debugger work if my server is under load?
166166
Yes - Snapshot Debugging can work for servers under load. The Snapshot Debugger will throttle and not capture snapshots in situations where there is a low amount of free memory on your server.

0 commit comments

Comments
 (0)