ed/raddebugger
1
0
Fork 0
mirror of https://github.com/Ed94/raddebugger.git synced 2026-08-06 22:08:41 +00:00
Code Issues Packages Projects Releases Wiki Activity

notes; skip relativization path for stdout/stderr/stdin paths

Browse Source
This commit is contained in:
Ryan Fleury
2025-05-20 11:00:18 -07:00
parent 34df269c58
commit 41ee0c83d4
4 changed files with 11 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/raddbg/raddbg_main.c
+3 -1
View File
@@ -15,12 +15,14 @@
- Stopped the debugger from running the default Windows message handling path for most `Alt`-based keybindings, which was causing a Windows beep sound to play.
- Fixed a bug where RDI files would sometimes fail to generate, resulting in no debug info being available on some runs.
- Fixed a bug which was preventing backslashes from working in file system querying interfaces correctly.
- Fixed a bug which was preventing some recursive callstacks from fully displaying in the debugger.
- Fixed a bug which was preventing some recursive call stacks from fully displaying in the debugger.
- Fixed a bug which prevented `Space` from being used as a keybinding. Bound `Space` by default to the `Accept` command (to which `Enter` / `Return` is also defaultly bound).
- Fixed a bug which was preventing conditional breakpoints from correctly being placed, if the condition expression did not evaluate when the debuggees were resumed.
- Fixed the debugger applying too much path processing, which was causing relative paths in debug info to be interpreted incorrectly. The debugger should now work much better with relative paths (e.g. produced via `/d1trimfile`). In these cases, the debugger may still not be able to fully compute the correct absolute paths, because this information is not stored within debug information. But once the debugger is redirected to the correct file once through the UI, it should work with relative paths correctly.
- If the debugger crashes, the message box which opens and displays the crash call stack now also allows the creation of crash dump files. Please submit these, if possible, with crash reports; it will help us to debug crashes more effectively.
- Fixed a bug which was causing text rendering to fail both when running the debugger on WINE and also on Windows 7.
- Fixed a bug where exception information inlined in source code would overlap the source code text.
- The debugger now correctly correctly interprets relative per-target `stdout`, `stderr`, and `stdin` paths.
*/
////////////////////////////////