I've been trying to get DDD 3.3.10 to work with dbg-cli version 2.11.32, built from source. After a lot of running around (your documentation is very sparse), I've gotten DDD to use dbg-cli as its sub-debugger:
ddd --debugger /usr/local/bin/dbg-cli &
|
.dbg_init contains something like:
set mode on
set mapurlroot http://localhost/
set maplocalroot /home/torenware/testdir/
set mapremoteroot /home/torenware/testdir/
|
I've set up the client to listen on port 11111, and when I do "listen" in the dbg command window, ddd pauses, and ddd finds my index.php.
But I can't get the stupid debugger to do anything useful once it finds the page. All attempts I've made via the DDD UI to set breakpoints cause errors. If I hit the ddd "break" button, for example, immediately after dbg detects I've hit the web page, I get something like this in the command window:
dbg>break includes
file name and line number must be separated by colon.
|
Everything else also gets errors.
Does you patch actually do any useful work
I'm aware that emphasis is on your paid application. But if the DDD patch is a good measure of the quality of the paid application, I'm not sure I want to invest either the time or money into it.
At a minimum, stop suggesting that dbg-cli works with DDD, or give enough documentation so that your users do not waste a great deal their time on an application that does not work.
Right now, I'm inclined to buy a debugger. But it won't be yours