Skip to content
#

debugger

Here are 765 public repositories matching this topic...

LGLTeam
LGLTeam commented Feb 24, 2020
  • 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

ppggff
ppggff commented May 18, 2018

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:

kyrylo
kyrylo commented Mar 21, 2019

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
rocallahan
rocallahan commented Apr 10, 2018

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.

carolstran
carolstran commented Oct 10, 2019

👋 I noticed that there are a couple of instances of words "easily" and "just" in your documentation. Unfortunately, words like this can make people feel frustrated and isolated while reading (myself included, hence the issue) - especially if they are facing issues.

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

processhacker
larz93
larz93 commented Feb 9, 2020

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

ryanflores-bayalarm
ryanflores-bayalarm commented Feb 13, 2020

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 
aultac
aultac commented Sep 26, 2019

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

akrantz
akrantz commented Mar 5, 2019

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": true in launch config):

Steps t

robbiesri
robbiesri commented Jun 4, 2019

If I look at the Capturing a Trace page, the page tells me how to capture a trace, but doesn't make any suggestions on what I should do for certain scenarios.

It would be awesome if the docs had some suggested workflows to use when tackling certain issues.

  • Debugging a rendering artifact?
    • Capture a single frame at the time the artifact is observed
    • C

Improve this page

Add a description, image, and links to the debugger topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the debugger topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.