[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
GNU Make debugger support - not sure I branched correctly
From: |
ddd |
Subject: |
GNU Make debugger support - not sure I branched correctly |
Date: |
Sat, 19 Nov 2005 23:03:19 -0500 |
I've changed the 30 or so files and made the hundreds of little
additions so DDD will support the new GNU Make debugger makedb.
As in the past, there were changes made in the debugger (makedb) to
facilitate things for ddd. By in large these debugger changes make the
debugger's interface look more like others, which is probably a useful
thing.
Although changes are in makedb's CVS, they are not part of a release
yet. So to use, either one needs to use what's in makedb's CVS (see
http://sourceforge.net/cvs/?group_id=61395 for instructions - the
module name is "remake"). Or one can wait until the next release which
will probably not be too long.
Likewise in order to beef up bash debugging support, a couple of new
commands were added to the bash debugger. No changes in ddd for bash
*require* the recent bash debugger changes, they just make use of it
if it is around.
I created a branch for the changes to support the GNU make
debugger. However I'm not sure I did things as was intended. I ran:
cvs tag -b makedb
and saw:
..
T .RELEASE
T .cvsignore
T ANNOUNCE
Then I commited - no problem. If I run
cvs log -h configure.ac
I see:
Working file: configure.ac
head: 1.67
branch:
locks: strict
access list:
symbolic names:
makedb: 1.67.0.2
DDD_3_3_11: 1.66
DDD_3_3_10: 1.64
But when I go to another copy I've checked out and do an "update" I
see that the changes I've made are applied by default. Perhaps this
has something to do with "HEAD"? I don't know. If it is desired to
change this, I'm not completely sure what is desired, let alone how to
fix.
- GNU Make debugger support - not sure I branched correctly,
ddd <=