public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17960] Internal error: tracker != NULL when completing on file:function
Date: Tue, 22 Feb 2022 16:04:26 +0000	[thread overview]
Message-ID: <bug-17960-4717-vNa4fvYOeZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17960-4717@http.sourceware.org/bugzilla/>

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

Keith Seitz <keiths at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |OBSOLETE

--- Comment #8 from Keith Seitz <keiths at redhat dot com> ---
(In reply to Tom Tromey from comment #7)
> Keith, is this still relevant, or can we close this PR?

Looks like this is no longer an issue (and hasn't been
for some time), so I'll close this. Thank you for pointing
this out.

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

      parent reply	other threads:[~2022-02-22 16:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12  1:04 [Bug gdb/17960] New: " keiths at redhat dot com
2015-02-12 23:45 ` [Bug gdb/17960] " dje at google dot com
2015-02-13 17:05 ` gbenson at redhat dot com
2015-02-13 17:32 ` keiths at redhat dot com
2015-02-27 16:50 ` keiths at redhat dot com
2015-02-27 18:29 ` dje at google dot com
2015-08-10 19:24 ` cvs-commit at gcc dot gnu.org
2015-08-10 20:39 ` cvs-commit at gcc dot gnu.org
2022-02-22 15:15 ` tromey at sourceware dot org
2022-02-22 16:04 ` keiths at redhat dot com [this message]

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