Bug 6439 - Watchpoints on more than one variable triggers incorrectly
Summary: Watchpoints on more than one variable triggers incorrectly
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Phil Muldoon
URL:
Keywords:
Depends on:
Blocks: 1625
  Show dependency tree / graph
 
Reported: 2008-04-21 20:02 UTC by Teresa Thomas
Modified: 2008-04-23 07:04 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Teresa Thomas 2008-04-21 20:02:44 UTC 
If watchpoints are set for two (or more) variables, a read/write into either one
of its location, causes updateHit() for both watchpoint observers to trigger.
(Same task)
Comment 1 Phil Muldoon 2008-04-23 07:04:27 UTC 
Watchpoints were being broadcast to all observers. Fixed.

- Log -----------------------------------------------------------------
commit 698d437d536d29ef47d59441c0dd88e8616e86a1
Author: Phil Muldoon <pmuldoon@redhat.com>
Date:   Tue Apr 22 09:12:00 2008 +0100

    Only notify watchpoint observers that have been triggered.
    
    2008-04-22  Phil Muldoon  <pmuldoon@redhat.com>
    
    	* LinuxPtraceTaskState.java (Running.checkWatchpoint): Check
    	write state on notify.
    	* LinuxPtraceTask.java (notifyWatchpoint): Collect only
    	watchpoints that have been triggered, then notify.
    	* LinuxPtraceProc.java (LinuxPtraceProc): Wide watchpoint scope
    	to protected.