This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [PRELIMINARY]: Patch to add bfd support for IBM s390
- To: DJBARROW at de dot ibm dot com
- Subject: Re: [PRELIMINARY]: Patch to add bfd support for IBM s390
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Fri, 25 Aug 2000 12:43:35 -0400 (EDT)
- CC: gdb-patches at sourceware dot cygnus dot com, nickc at cygnus dot com, msnyder at redhat dot com
- References: <C1256946.0041A357.00@d12mta09.de.ibm.com>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> From: DJBARROW@de.ibm.com
> Date: Fri, 25 Aug 2000 13:56:54 +0200
>
> To be honest it was a long time ago, it was primarily to do with
> watchpoints set up in hw being
> inconsistent with what info watchpoints said was active.
>
> e.g. The watchpoint code cleaned the hardware breakpoints in the next run
> while info watchpoints
> still reported watchpoints active ( this kind of stuff )
I don't think I've seen such problems in v4.18. Is it possible that
you are confusing between the insert/remove watchpoints mantra that
GDB does each time before it resumes the debuggee and after the
debuggee stops, with the actual deletion of the watchpoints (when the
user says "delete NN")? (Sorry for asking the obvious.) GDB always
removes the watchpoints after the debugge stops, but that doesn't mean
they shouldn't appear in the "info break" report.
> I'll do some testing over the next few days & if it still looks unhealthy
> I'll start complaining.
Sure, please do.