your feedback send to: debugger@fyzor.com     
C++ debugger
Navigator
Main
Screenshots
Docs
Download
Sources
Plugins
API
History
Legend
Contacts
Links
Mail
Search
Search Site With Google
Надежный хостинг по доступным ценам!

Legend

Sorry for my broken english guys, I only guess what some of you think reading these masses of words, but there is nothing in the world that can stop me to express my feelings. So, let me begin...

IDE and monopoly

At first I must clear one thing about myself: instead any IDE I always prefer to use the command line tools and file managers similar to FAR. The reason why I do it is simple: IDE's are too complicated and inconvenient, has many excessive and rarely used "functionality", and their logic of work is hidden and not sufficiently clear. All that restricts the freedom of their possible usage, and, as a result, slows down the process of development.

And I think things couldn't be different from that, because it is a common tendency of giant software companies to try to establish a monopoly of their products by gathering all user demands into one single "Super Product". This desire, as I strongly believe, is not a result of thinking about their users (at least, the best of them), but instead is a kind of inspiration to crush down one's competitors and to take up the market.

But as a result of this monopoly is the lost of quality and universality of such IDE's.

Idea of constructor

By all these reasons I prefer to assemble my personal "development environment" by myself, and to use for that different products from many different sources. Doing so, the programmer gets exactly the same environment that he wants and finds effective to himself. Also he gets a way to replace any of the parts of his system in any time by the newer or by more convenient ones. You get the freedom and flexibility, and that is what we need to work efficiently.

This particular desire for freedom and reluctance to lock myself to constraints created by others - makes it impossible for me to use IDE, and motivates to seek and use stand-alone development tools. Also the urge of this freedom was the primary reason why for a long time I used compiler from Borland. Not only the abstract "freedom" from Microsoft was the reason for that, but also there was a big plus - the stand alone debugger TD for which there were no better alternatives even now.

Analysis of The Market

While the time went on, the TD debugger was getting older and older, and no new versions for it were not issued at all, making old bugs more annoying. Not surprising that someday has come the moment when I has encountered a serious bug, that has finally forced me to leave completely Borland's compiler and its antediluvian debugger, and to start using Visual C, hoping someday to find a great debugger for it.

But these hopes had failed; testing a number of well-known but inconvenient debuggers I didn't find anything useful for me. The only result of my trials was the analysis of the market and remarkable inference that this software niche seems to be absolutely empty and its filling in is not a line of near future. That was the thought leading me to start to work. Plus there were other two reasons: 1) desire to get universal and simple tool for debugging, 2) to check out some my private ideas of how it all MUST BE.

Logfile

Maybe it sounds like a joke or a bad promotion method, but truly saying while I was working on this project, I still had no debugger "to debug the debugger", and because of that have developed and used another, alterative techniques to debug. I mean the log file and the special crash-catching modules that radically simplified the process of searching for errors.

Based on that experience was my next paradoxic inference: for big projects it will be sufficient and fully effective to create a special debugging system built in directly into your project. Yes, it requires some tricks and additional work - primarily textual representation for important structures and variables - but it rewards you later by simplifying you debugging.

But for small projects this additional work and "supervisor" system does not justify the time that was spent to create it. And that is where our Zeta Debugger. is coming in.

Resume

So, we think our product will be ideal for You, if You:

  • prefer to use the keyboard in place of mouse
  • prefer to manage your own development environment using stand-alone tools,
  • want to be independent of any specific compiler
  • love simplicity and clarity in your work and workbench
  • like to dig into program code for the sake of self education
  • like to dig into Windows itself for the same purpose

    Future

    Firstly, I plan to make the Debugger more stable, and then to wait while its development repays the time I've spent. May be after year or two I will publish here all debugger's source files. But currently I am not sure about that.

    Statistics:

    The entire project is written in pure C. At the moment I write these lines, it takes 1050Kb in size, and this project contains more than 35 thousands of lines. Total amount of C files is 132 of .c and .h. It uses only Windows API and doesn't use any third party DLL's.

  • Project and site author: Sapunov Vladimir
    (c) Copyright 2005-2008