This is the mail archive of the
mailing list for the GDB project.
RE: [PING][RFA-v2] Fix troubles with watchpoints in DJGPP
This is perfectly OK for me,
could you check it in?
Otherwise I can check it in tomorrow.
Thanks for your replies
> -----Message d'origine-----
> De?: email@example.com [mailto:gdb-patches-
> firstname.lastname@example.org] De la part de Pedro Alves
> Envoyé?: Wednesday, June 17, 2009 1:46 AM
> À?: Pierre Muller
> Cc?: email@example.com; 'Eli Zaretskii'
> Objet?: Re: [PING][RFA-v2] Fix troubles with watchpoints in DJGPP
> On Wednesday 17 June 2009 00:20:06, Pierre Muller wrote:
> > + ?/* On systems that load no shared libraries, like DJGPP target,
> > + ? ? breakpoint_re_set is never called.
> > + ? ? Call it now so that ordinary watchpoints get a chance to
> > + ? ? become promoted to hardware watchpoints if the pushed target
> > + ? ? supports hardware watchpoints. ?*/
> > + ?breakpoint_re_set ();
> > +
> Much, much better, thanks. "systems that load no shared libraries"
> still isn't the right predicate, as I demonstrated with the
> linux static executable, and the breakpoint_re_set call due to
> adding the vsyscall page's symbols. I'd suggest expanding a bit
> more. Something like:
> /* If the user sets watchpoints before execution having started,
> then she gets software watchpoints, because GDB can't know which
> target will end up being pushed, or if it supports hardware
> watchpoints or not. breakpoint_re_set takes care of promoting
> watchpoints to hardware watchpoints if possible, however, if this
> new inferior doesn't load shared libraries or we don't pull in
> symbols from any other source on this target/arch,
> breakpoint_re_set is never called. Call it now so that software
> watchpoints get a chance to be promoted to hardware watchpoints
> if the now pushed target supports hardware watchpoints. */
> breakpoint_re_set ();
> (s/ordinary/software/. There's nothing unordinary about hardware
> Pedro Alves