public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/29868] [gdb/tdep, s390x] breakpoint.c:5784: internal-error: bpstat_stop_status_nowatch: Assertion `!target_stopped_by_watchpoint ()'
Date: Mon, 12 Dec 2022 09:46:54 +0000	[thread overview]
Message-ID: <bug-29868-4717-tCytYy7jPs@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29868-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29868

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)
> we try to clear the watch point status in
> s390_linux_nat_target::stopped_by_watchpoint to make sure that we "Do not
> report this watchpoint again".  That doesn't seem to have any effect though,

And that seems to be documented behaviour, in ./arch/s390/kernel/ptrace.c, in
__poke_user_per we have:
...
        /*                                                                      
         * There are only three fields in the per_info struct that the          
         * debugger user can write to.                                          
         * 1) cr9: the debugger wants to set a new PER event mask               
         * 2) starting_addr: the debugger wants to set a new starting           
         *    address to use with the PER event mask.                           
         * 3) ending_addr: the debugger wants to set a new ending               
         *    address to use with the PER event mask.                           
         * The user specified PER event mask and the start and end              
         * addresses are used only if single stepping is not in effect.         
         * Writes to any other field in per_info are ignored.                   
         */
...

So, the bits that we're trying to clear here in per_struct.lowcore, after the
fields listed above.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-12-12  9:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10  8:18 [Bug gdb/29868] New: [gdb, s390x -m31] " vries at gcc dot gnu.org
2022-12-10 11:25 ` [Bug gdb/29868] [gdb, s390x] " vries at gcc dot gnu.org
2022-12-12  3:14 ` [Bug tdep/29868] [gdb/tdep, " vries at gcc dot gnu.org
2022-12-12  9:46 ` vries at gcc dot gnu.org [this message]
2022-12-12  9:48 ` vries at gcc dot gnu.org
2022-12-12 12:08 ` vries at gcc dot gnu.org
2022-12-12 13:51 ` uweigand at gcc dot gnu.org
2022-12-12 15:08 ` vries at gcc dot gnu.org
2023-01-11  9:26 ` vries at gcc dot gnu.org

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=bug-29868-4717-tCytYy7jPs@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).