public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "xdje42 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/17285] New: watchpoints: is using ALL_LWPS ok?
Date: Sun, 17 Aug 2014 23:19:00 -0000	[thread overview]
Message-ID: <bug-17285-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 17285
           Summary: watchpoints: is using ALL_LWPS ok?
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
          Assignee: unassigned at sourceware dot org
          Reporter: xdje42 at gmail dot com

Was looking into what's involved in removing lwp_list and came across this.
Filing so I don't forget it.

x86-linux-nat.c uses iterate_over_lwps to only update debug regs for the
current inferior.  Other ports use ALL_LWPS (grep ALL_LWPS *.c) which will
iterate over all threads in all inferiors.

The difference is odd.  Is there a bug here?

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


                 reply	other threads:[~2014-08-17 23:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-17285-4717@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).