Date: Tue, 04 Sep 2001 19:26:27 +0300 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: "Andrew Cottrell" Message-Id: <2593-Tue04Sep2001192626+0300-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9 CC: djgpp-workers AT delorie DOT com In-reply-to: <001901c1353d$f73fdf40$0a02a8c0@acceleron> (acottrel@ihug.com.au) Subject: Re: DJGPP & Windows 2000 package updated for testing References: <009601c12dd7$e55b50b0$0a02a8c0 AT acceleron> <003401c13347$bedddc30$0a02a8c0 AT acceleron> <001901c1353d$f73fdf40$0a02a8c0 AT acceleron> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: "Andrew Cottrell" > Date: Tue, 4 Sep 2001 22:34:38 +1000 > > The only outstanding issue with regards to DJGPP and Win 2K with the > available packages is that in Bash 2.05 the set command may be causing > issues with re-configuring packages and as such you may not be able to > re-configure or re-build the packages on Win 2K until this is resolved. There's one more known issue, discovered a few days ago by Charles: hardware-assisted breakpoints and watchpoints don't work. More accurately, the functions in src/debug/common/dbgcom.c which are invoked by all the debuggers to insert and remove hardware breakpoints and watchpoints via DPMI functions (because debug registers cannot be accessed directly under DPMI)--these functions seem to be broken on W2K in some weird way. (You can set a watchpoint, but once set, it seems like it cannot be removed, and gets ``stuck'' in the DPMI host until you kill the DOS box.) As a result, edebug32 and FSDB are almost completely broken and barely work, because they use hardware breakpoints for the first 4 breakpoints. GDB does work as long as you dont use `hbreak' and `watch' (or `rwatch'/`awatch') commands.