Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [rfc, rfa/doc] Multi-threaded watchpoint improvements
Date: Wed, 16 Apr 2008 22:57:00 -0000	[thread overview]
Message-ID: <jeej95ctk8.fsf@sykes.suse.de> (raw)
In-Reply-To: <20071001002015.GA15835@caradoc.them.org> (Daniel Jacobowitz's 	message of "Sun, 30 Sep 2007 20:20:15 -0400")

Daniel Jacobowitz <drow@false.org> writes:

> 2007-09-30  Daniel Jacobowitz  <dan@codesourcery.com>
> 	    Jeff Johnston  <jjohnstn@redhat.com>
>
> 	* breakpoint.c (watchpoints_triggered): New.
> 	(bpstat_stop_status): Remove STOPPED_BY_WATCHPOINT argument.
> 	Check watchpoint_triggered instead.  Combine handling for software
> 	and hardware watchpoints.  Do not use target_stopped_data_address
> 	here.  Always check a watchpoint if its scope breakpoint triggers.
> 	Do not stop for thread or overlay events.  Improve check for
> 	triggered watchpoints without a value change.
> 	(watch_command_1): Insert the scope breakpoint first.  Link the
> 	scope breakpoint to the watchpoint.
> 	* breakpoint.h (enum watchpoint_triggered): New.
> 	(struct breakpoint): Add watchpoint_triggered.
> 	(bpstat_stop_status): Update prototype.
> 	(watchpoints_triggered): Declare.
> 	* infrun.c (enum infwait_status): Add infwait_step_watch_state.
> 	(stepped_after_stopped_by_watchpoint): Delete.
> 	(handle_inferior_event): Make stepped_after_stopped_by_watchpoint
> 	local.  Handle infwait_step_watch_state.  Update calls to
> 	bpstat_stop_status.  Use watchpoints_triggered to check
> 	watchpoints.
> 	* remote.c (stepped_after_stopped_by_watchpoint): Remove extern.
> 	(remote_stopped_data_address): Do not check it.

That completely broke watchpoints on ppc.  They are no longer recognized
as such, and gdb is reporting a SIGTRAP instead.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  parent reply	other threads:[~2008-04-16 22:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-16 18:40 Daniel Jacobowitz
2007-09-22  9:03 ` Eli Zaretskii
2007-09-22 14:04   ` Daniel Jacobowitz
2007-09-22 14:13     ` Eli Zaretskii
2007-09-22 15:37       ` Daniel Jacobowitz
2007-09-22 15:46         ` Eli Zaretskii
2007-09-22 18:28           ` Daniel Jacobowitz
2007-10-01  0:20 ` Daniel Jacobowitz
2007-10-24 14:59   ` Luis Machado
2007-10-24 16:00     ` Daniel Jacobowitz
2007-10-24 16:42       ` Luis Machado
2007-10-24 16:51         ` Daniel Jacobowitz
2007-10-24 18:08           ` Luis Machado
2007-10-24 18:20             ` Daniel Jacobowitz
2008-04-16 22:57   ` Andreas Schwab [this message]
2008-04-16 23:05     ` Daniel Jacobowitz
2008-04-16 23:18       ` Andreas Schwab
2008-04-17  0:25         ` Daniel Jacobowitz
2008-04-17  9:52           ` Andreas Schwab
2008-04-17  9:59             ` Andreas Schwab
2008-04-17 10:17           ` Andreas Schwab
2008-04-17 14:53             ` Daniel Jacobowitz
2008-04-20  2:35               ` Andreas Schwab
2008-04-23 11:55                 ` Andreas Schwab
2008-04-23 19:46                   ` Eli Zaretskii
2008-05-01 19:30                   ` Daniel Jacobowitz
2008-05-01 19:50       ` Luis Machado

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jeej95ctk8.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox