debugger
Here are 765 public repositories matching this topic...
-
What version did you use? 6.1.3 (dc32a40)
-
Write down all steps needed to reproduce this issue. Also attach any needed files.
This is very annoying when I was about to save the file (File -> Save or FIle -> Save all). Hours of work lost when a file/folder selection dialog freezes and crashes. As a workaround, I could have typed the path manually
This is very hard to reproduce crash bec
When casting to a pointer with a package type, delve give error, such as:
(dlv) p *(*aaa/bbb/ccc.DDD)(0x134234234)
Command failed: no type entry found, use 'types' for a list of valid types
But I got this expr from a result of printing another map, so the type must be right.
After reading the source file about type casting in delve,
I found in delve/pkg/proc/types.go:
the above is a usually appeared screen-shot in jupyter notebook, if colored in columns, it would be really helpful to distinguish time/line number/code/variables parts.
Add a field on the breakpoint that shows the number of times a breakpoint was hit. See The -break-list Command.
let devtools: any = window['devToolsExtension'] ? window['devToolsExtension']() : (f:any)=>f;
let middleware = applyMiddleware(thunk);
const store: any = middleware(devtools(createStore))(rootReducer, {});
-
Updated
Mar 5, 2020 - Python
Currently, we have 2 ways of printing text:
- through
output(e.g.output.puts) - through
_pry_.pager.page
I can see a few problems here:
_pry_is a God object, which is awful. Commands have to pry into_pry_to get what they need. Any kind of modification to_pry_is a big risk of breaking something since some command may depend on something we didn't intend to share- co
There's a timing issue that means they need re-running fairly frequently, and they seem to be completely broken at the moment so I've disabled them.
gdb supports QPassSignals as a way to tell the agent about signals that should be passed directly to the debuggee without being reported to gdb. Supporting this could greatly speed up reverse execution when many gdb-ignored signals have been delivered, e.g. SIGSYS in Firefox sandboxed content processes.
If it's alright with your team, I'd like to take a shot at updating the content to make it more inclusive by removing instance
-
Updated
Mar 8, 2020 - Swift
For music application (like foobar2000), i can get more clean sound quality by setting one core to the process exclusively. Process hacker only supports setting affinity for one process a time. I hope adding the feature for setting affinity for multiple selected processes a time.
1.select all processes and set affinity to core 0, 1, 2.
2.select foobar2000 and set affinity to core 3, now foobar20
The byebug guide at https://github.com/deivid-rodriguez/byebug/blob/master/GUIDE.md has a link to "https://github.com/deivid-rodriguez/byebug/blob/master" titled "See Byebug.start with a block."
This is a dead link now, but where was it meant to be linked to?
-
Updated
Mar 11, 2020 - TypeScript
I got the information on IRC, but I have since lost the chat message due to a computer crash
These would be awesome:
- Update documentation on how to do it
- Provide a starting template
- UI to be able to define your own interpreter
The adapter stopped working for me yesterday while using Chrome on Macos 10.15.3. When I tap the Inspect link, a blank window launches. When I open a separate console window for the Inspect window, I'm Seeing the following error:
Uncaught TypeError: document.registerElement is not a function
at Object.UI.registerCustomElement (inspector.js:2927)
at inspector.js:2938
at
When setting a non-existent path in the state (using a tag and store.set), if devtools is turned off the path in the state is created appropriately. When devtools is turned on, the browser throws an error about reading a property of undefined on line 93 of Store.js in cerebral. The Cerebral debugger shows the value in the state as if it had been set appropriately in the first place.
To reprod
Debugging Office Add-ins running in Chrome will work, meaning breakpoints will be hit, when using the Chrome browser dev tools. However, when using VSCode Debugger for Chrome, the breakpoints will not be hit. It appears that the extension does not handle scriptParsed messages for source inside of an iframe.
- VS Code Version: 1.31.1
- Log file (set
"trace": truein launch config):
Steps t
This happens consistently on my machine. To reproduce:
- pip install tensorflow
- pudb3 pudberror.py
- set breakpoint on line 5
- print x twice in command line
pudberror.py
import tensorflow as tf
x = tf.compat.v1.placeholder(tf.float32, shape=(1024, 1024))
print(x)
Adding link to https://github.com/android10/frodo2 might be useful as well.
I wonder why nobody every asked for this, shouldn't this be a common feature?
This feature would reduce tediousness when having to run multiple "Fill with NOPs" or "Fill with 00s" or "Binary Edit".
Improve this page
Add a description, image, and links to the debugger topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the debugger topic, visit your repo's landing page and select "manage topics."



add please to sdk