x13pixels / remedybg-issues Goto Github PK

[direbroom]

[Recryllic]
Pointers in the watch window get displayed with all of their zeros, which is a bit unreadable. I'd suggest either removing the leading zeros or graying them out.

[Recryllic]
Breakpoints are stored in the .rdgb which makes it kinda annoying to close the program as it pops up a dialog.

[Recyrillic]
The page up/ page down for the memory widget should snap to the top/ bottom so that you can view memory along a page boundary more easily.

[Niklas L.]

It runs into an "int3" in D3DSCache.dll when running my game's rendering code.
Pressing F5 more than once crashes RemedyBG.

[direbroom] (super minor): the first column in watch/threads (the one with the yellow arrow) should be fixed size even when expanding/shrinking columns or the window to always fully show the arrow, no less or empty space after

Use checksums in PDB to determine if the source file on disk matches or not. If not, then display an indicator on the text window's title bar.

[Simon A.]
There seems to be some small latency while moving in the source view. I'm on Windows 7 with the compositor off and something feels wrong. One off the thing that I saw that might be an illustration of the problem is that when using page up / page down in a specific file, I could see that the text cursor was moving up to one line before the top of the view, and than a frame or so latter the view was moved a little bit. I joined a video (remedybg_latency.mp4), if you go frame by frame you can count up to 4 frames between the cursor move and the view move (at 30fps).

[direbroom]

See https://docs.microsoft.com/en-us/visualstudio/debugger/debug-using-the-just-in-time-debugger?view=vs-2019

[casey, simon] Need to be able to type an expression into the watch window

[Simon A.]
...while in a source file, with the cursor (text cursor) on the last line of a file, keeping the up arrow pressed to move up the file, the cursor "drifts" to the bottom of the view. In most application pressing up will move the cursor to the "first line of the view", and than scroll the file and keep the cursor on the first line of the view. In remedybg, it either stays at the bottom or moves to about 2/3 of the view, than start scrolling and the cursor doesn't stay at the same position, overtime it goes down until it goes of the screen or view (doesn't happen all the time). See attached video remedybg_cursor.mp4. This may be related to using Page Up/Page Down or Ctrl + end/Ctrl + home to go to the bottom of the file. Sometimes, when reaching the top in such a way, the view stops with one line still of screen and need to wait for the cursor to reach the top to display that line. Moving the cursor is also jittery, the cursor doesn't seem to know on which line it is. Going down works ok, but you can see the jerkiness of it.

The source view movement is still off (I don't know if you try to fixed it yet so I report it again). The cursor still moves before the view moves and It gives a bad visual feedback/feeling.

[michael] Every time I open Remedy, the Memory, Registers and Disassembly window are unchecked. When I start debugging I recheck them and they reappear where I expect them to be. This happens with the default layout and a customized one.

[direbroom]
disasm window should have an input field where I can write/paste an address and disasm will jump there

[direbroom]
Register highlighting (when clicked on/selected) in disasm window

[direbroom, simon, casey, et al.] when entering an address in the mem window, either start the window text at that address (not aligned), or highlight the byte of the address jumped to

[direbroom]

When I press Alt or Alt GR when in another windowed application, RemedyBG still get the messages, and the UI is updated which is distracting (tabs lights up).

[direbroom]
Option for single thread stepping (aka, F10/F11 only resumes the current thread and step there)

[direbroom]

[casey]
My recommendation would be to add "symbols" settings, honestly. It would have a few simple settings in it, like checkboxes for "search the system path" and "search the directory where the executable was" and stuff like that, for auto-hunting PDBs. It should also have a "symbol path" text box, or list, or whatever, where the user can specify paths to search for symbols. There should probably also be one that's like "project-specific symbol search path", which you would put below the working dir, and you'd save it along with the project?

Finally, the other really nice feature that you probably want is some way to set symbols per module. So like, if all else fails, the user can browse the module list, and say "hey this specific module right here, this is where to get the PDB from it, and by the way, give me a checkbox to override GUID matching so that I can force you to use a PDB for it even if it's wrong.

Alt tabbing from remedybg to another application and back doesn't work well because it seems to give the source file tabs the focus (probably because of the ALT key).

[Recryllic]
Breakpoints are stored based only on line number as far as I can tell, this gets annoying, as you are probably debugging the part of the program, that you change a lot.

[Simon A.]
Would it be possible to right click on the column names to choose which column to display (I never need the Type column). This would be nice in every list in the UI;

[michael] Both Control and Session menus have a Start Debugging but only Session shows a Stop Debugging. It would be useful if Control also had the stop action and maybe the restart as well. I keep looking for these there since I'm using the Control menu to initiate debugging.

[Omar]
Say I have a large array of structure,

• First I'd want to easily display selected field prominently (e.g. show me a quick preview with all "Name", "ID", "Pos")
  The static .natvis mechanism of Visual Studio is not good enough, because the fields we actually want to see change all the time!
  There should be enough support UI do you can select the root of an array, enter a shortcut and then input some text e.g. "Name" and you see the Name of all entries, and you can quickly add/remove that variable from the one-liner preview shown in the watch.
  The debugger could remember a list of the frequently used one-liners preview per data structure type so you can quickly change between them.

• Then I want to easily do some filtering over my large sets.
  Maybe manual tagging/hiding of certain instances and then display only the tagged or not hidden instances?
  That's pretty simple/dumb and yet even this would be extremely valuable for debugging.

• Or use selection script, to filter dynamically or to filter once and saved the filtered result.
  "only show instance where (Flags & 0x1000000) != 0"
  "only show instance where Name starts with "Hello""

[direbroom]

[direbroom] (super convenience): "nop" an asm instruction in the disasm window

[direbroom]

When scrolling, the column headers for a table should remain visible.

When double clicking on an expression to start editing it, it would be nice to be able to also click on the line to place the cursor.

[Casey]
It'd be nice if the watch window values that change during a step were highlighted in red until the next run/step.

[direbroom]

We'll want to be able to see inline functions in the call stack.
We'll want to set a breakpoint on an inline function and set breakpoints at all of the inline'd sites.

[direbroom, casey, et al.]
enable select/copy in (most) windows (e.g. i want to copy the address from the disasm window and paste in the memory window)

[direbroom]
Keyboard re-binding (specifically I'd love to bind "Control->Break" to a key).

[forestthewoods] Is there no way to attach RemedyBG to an existing process? This is strictly required by my workflow. :(

Allow additional watch and memory windows.