Hello guys! A new build is here and lets see what is new.

• Added Unicode support to the rendering system.

• Fileviewer will open files that are encoded as UTF-8.

• Fileviewer now has indentation lines that can be toggled from the config file through the "fileviewer_show_indent_lines" value modifier.

• Added a config value modifier "fileviewer_tooltip_timer_ms" that changes delay of the value tooltip in the Fileviewer widget.

• Added a config value modifier "maximize_window_on_start" that maximizes debugger's window on startup on startup if set to "true".

• Added a config value modifier "tab_width" that changes default tab width.

• Added a new config event "clear_all_expr" that clears all the expressions in the inspector. Currently bound to CTRL + l.

• Added a new config event "clear_all_data_bp" that clears all the data breakpoints. Currently bound to CTRL + g.

• C/C++ Lexer now can parse integer suffixes like 0x123ull.

• String v

Hello guys! A new build is here and lets see what is new.

• Now you have an ability to change values on the fly in the Inspector widget. Double click on the value or press CTRL+e to edit.

• Run-to a line is now available. You can access it with shortcut 't' in Fileviewer widget or right click and select in the context menu "Run To Cursor". Also you can set next statement with shortcut 'r' or right click and select in the context menu "Set Next Statement".

• A file dialog will show up now when missing a file. This helps when your source code directory does not match hard-coded directory in the debug info file.

• Now when a new expression is created Inspector will select next empty row.

• A bug with AltGr was fixed.

• Added shortcuts to quickly access different panes. ALT+1 - Selects Fileviewer ALT+2 - Selects Inspector ALT+3 - Selects Callstack ALT+0 - S

Hello guys!

It has been a while since I posted something here, the reason is that a series of unfortunate events occurred in my life which prevented me from programming at all. Only last October I returned back to my normal life, and first thing that I did was firing up emacs and checking out state of the debugger. First impulse was to burn everything to the ground and start over, but lucky me that a more rational thought followed it. Starting over will not change anything, and it is better to work on the existing code. After looking around I decided that it is time to get rid of the DIA library (Microsoft's COM disaster to read PDB). At the start I was not even sure that I will be able to write a replacement for that, however as time went by I found that there is nothing hard about it. I limited parser to a certain subset of symbols, which helped a lot because PDB has a lot of legacy stuff in it. Removing the DIA also forced me to write a stack unwinder. It is always a good th

Hello everyone! A new CDbg build is here. You can download build using this link. All instructions you can find inside the zip file.

Hello everyone, today I finally upload a new CDbg build.

Usage: - Starting: cdbg -t <PATH_TO_EXECUTABLE> - Switching between windows ALT+<arrow_key> - Switching between tabs CTRL+TAB go forward, CTRL+SHIFT+TAB go backward. - Launch debugee F5, Stop debuggee SHIFT+F5 - Stepping over F1, Stepping into F2 - Set breakpoint at function CTRL+B - Set breakpoint at selected line CTRL+Q - Goto line CTRL+G - Option menu CTRL+O - Debuggee command line arguments CTRL+E

Changes that were made: - Added keyboard navigation to the file viewer. - Clicking on call in "Call Stack" window brings you to the call location. - UI improvements. - Improved PDB symbol reader. - Reworked inspection window. - Lots of bug fixes.

Download here: link

Hello everyone! Today I upload a new version of CDbg with some improvements and bug fixes. Changes:

• File reloading
• Window to set function breakpoints (CTRL+B)
• Hot code reloading works
• Improved breakpoint system

Here is a video where I demo these changes: <bad video URL>

Download link - here

Hello everyone! In this post I want to tell you about my debugger. When I started to write this debugger I decided that first of all I will implement basic functionality that every debugger must have.

At this point debugger is capable of doing basic code stepping:

Inspecting stack:

Data inspection:

Setting breakpoints:

And viewing debug output:

Also I'm releasing first build, which you can download here: link