Menu
Is there a way to export the call stack when the code is stopped on a breakpoint?
I have very long ID strings that I need to grab for use in another program (see pic), and retyping from a screen capture is not really an option ;-)
I'm clicking around in the XE2 IDE but can't find anything.
(Workaround: For now I continue stepping through the code after the breakpoint, until I have moved far enough back up the stack that the local variables are available again.)
761
To open the Call Stack window in Visual Studio, from the Debug menu, choose Windows>Call Stack. To set the local context to a particular row in the stack trace display, select and hold (or double click) the first column of the row.
View the call stack while in the debugger While debugging, in the Debug menu, select Windows > Call Stack or press ctrl + alt + C . A yellow arrow identifies the stack frame where the execution pointer is currently located.
View the Call Stack To view the call stack, open DevTools Sources panel and on the right panel, expand the Call Stack panel to see all the current functions in the call stack.
To set a breakpoint in the Call Stack window: To open the Call Stack window, you must be paused during debugging. Select Debug > Windows > Call Stack, or press Ctrl+Alt+C. In the Call Stack window, right-click the calling function and select Breakpoint > Insert Breakpoint, or press F9.
To break at the instruction or line that a calling function returns to, you can set a breakpoint in the Call Stack window. To open the Call Stack window, you must be paused during debugging. Select Debug > Windows > Call Stack, or press Ctrl + Alt + C.
To save or share the state and location of your breakpoints, you can export or import them. To export a single breakpoint to an XML file, right-click the breakpoint in the source code or Breakpoints window, and select Export or Export selected. Select an export location, and then select Save. The default location is the solution folder.
The call stack includes an entry for each function called, as well as which line of code will be returned to when the function returns. Whenever a new function is called, that function is added to the top of the call stack.
The call stack debug window supports the usual selection and clipboard shortcuts. So use CTRL+A to select the entire call stack, and CTRL+C to copy to the clipboard. Or you can select a single item and copy with CTRL+C. Or you can select multiple items with CTRL+click and SHIFT+click, and so on.
184
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
