Re: [RFC]: x86 threaded watchpoint support [2/3]

[jjohnstn <jjohnstn@redhat.com>]

On Tue, 15 Jun 2004, Ulrich Weigand wrote:

> 
> 
> 
> 
> 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 ...
>

Actually, I believe this patch needs to be reworked.  It is causing a 
failure for ia64 watchpoints.  There are a number of problems to be looked 
at.  First of all, the stopped_by_watchpoint flag only gets set if 
HAVE_CONTINUABLE_WATCHPOINT is true.  Thus, any platform that doesn't 
define this macro or have the low level target 
to_have_continuable_watchpoint value set, will never set the 
stopped_by_watchpoint flag.  The logic in 
bpstat_stop_status ignores all hardware watchpoints if the flag is not set 
so we never do the value comparison.

Another problem is that some watchpoints are stepped (i.e. the signal 
occurs before the value is actually changed).  When we step over the 
watchpoint, again the flag won't get set because we have actually trapped 
due to a step operation, not a watchpoint.

 > Do you have more details about n what situation is this still 
not > enough?
> 

Knowing at least one watchpoint triggered is not enough detail. Gdb then 
has to check all values for change.  We may not stop all threads until 
multiple watchpoints change.  Now, imagine you have 1000 threads.  Even 
if we get one thread correct, the end-user has to do an info threads and search 
the other 999 threads to figure out where the other values got changed.  I 
personally use a watchpoint when I know a value has changed but can't 
figure out why it changed or there is some particular transition of value 
I am interested in.  In some cases, gdb won't be able to tie the 
thread to the watchpoint but where we can do so, we definitely should.

-- Jeff J.


 > 
> 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
> 
>