public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17626] attach, detach, attach did not work
Date: Fri, 05 Jun 2015 13:36:00 -0000	[thread overview]
Message-ID: <bug-17626-4717-xEB59H0O4R@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17626-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Gary Benson from comment #4)
> Version 2 patch here:
> 
>  https://sourceware.org/ml/gdb-patches/2015-06/msg00080.html

I'm curious why it doesn't check the buildid.
It seems to me that if the current file has a buildid
and the attach target has a buildid, and they do not match,
then discarding the current file is the best thing to do.
My recollection is that gdb can't always do this because
(on systems without buildid) the user might have meant to do
this weird thing.  But when buildid is available can it ever
be meaningful?

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


  parent reply	other threads:[~2015-06-05 13:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 16:19 [Bug gdb/17626] New: " tromey at sourceware dot org
2014-11-19 16:36 ` [Bug gdb/17626] " palves at redhat dot com
2014-11-19 21:01 ` tromey at sourceware dot org
2015-05-11 13:42 ` palves at redhat dot com
2015-06-05 13:36 ` tromey at sourceware dot org [this message]
2024-01-02 17:23 ` ssbssa at sourceware dot org
2024-01-10 23:20 ` tromey at sourceware dot 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-17626-4717-xEB59H0O4R@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).