This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC]: x86 threaded watchpoint support [2/3]
- From: Ulrich Weigand <Ulrich dot Weigand at de dot ibm dot com>
- To: jjohnstn at redhat dot com
- Cc: gdb-patches at sources dot redhat dot com, eliz at gnu dot org
- Date: Tue, 15 Jun 2004 17:17:07 +0200
- Subject: Re: [RFC]: x86 threaded watchpoint support [2/3]
Jeff Johnston wrote:
>The change is needed because with the threading model, you can have
>multiple events to process. So, if you check your watchpoint values,
>all of them may have changed but you end up reporting an invalid thread
>location. For example, I was getting watchpoints changing at the same
>time of a new thread event (it couldn't discern).
Isn't it enough to know whether you got the SIGTRAP because of a (any)
hardware watchpoint, or for some other reason (e.g. new thread event)?
*This* information is available on s390, and as of this patch:
http://sources.redhat.com/ml/gdb-patches/2004-05/msg00290.html
it is actually used to prevent bpstat_stop_status to recognize
a watchpoint event unless the kernel says it was a watchpoint ...
Do you have more details about n what situation is this still not
enough?
Mit freundlichen Gruessen / Best Regards
Ulrich Weigand
--
Dr. Ulrich Weigand
Linux for S/390 Design & Development
IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen
Phone: +49-7031/16-3727 --- Email: Ulrich.Weigand@de.ibm.com