From: acottrel AT ihug DOT com DOT au Message-Id: <200109042314.JAA31780@new-smtp2.ihug.com.au> X-Authentication-Warning: new-smtp2.ihug.com.au: Host kumera.ihug.com.au [203.109.250.78] claimed to be gnome.tabnsw.com.au To: Eli Zaretskii , "Andrew Cottrell" , djgpp-workers AT delorie DOT com Subject: Re: DJGPP & Windows 2000 package updated for testing Date: Tue, 4 Sep 2001 23:14:30 GMT X-Mailer: Endymion MailMan Standard Edition v3.0.24 Reply-To: djgpp-workers AT delorie DOT com > > 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. > Thanks for the update. I need to modify the site to indicate that GDB hardware breakpoints don't work. The site does not have edbug32 ot FSDB as far as I know unless they are included in some other package I built. I will check this tonight before updating the info at the site. Thanks, Andrew