Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
	Pedro Alves <palves@redhat.com>,
	gdb-patches@sourceware.org
Subject: Re: [RFAv2] Ensure 'exec-file has changed' check has priority over 'exec-file-mismatch' check
Date: Sun, 21 Jun 2020 07:42:26 -0400	[thread overview]
Message-ID: <ea766da5-c312-7e5b-afae-ebc8285ac1f9@simark.ca> (raw)
In-Reply-To: <013e37e14e361f8111eb7d2483429fa7328492c1.camel@skynet.be>

On 2020-06-21 7:30 a.m., Philippe Waroquiers via Gdb-patches wrote:
> Now, maybe many users will not know what is a build ID,
> and the more cryptic message might confuse them.

I think it's useful to mention how GDB reached the conclusion that
there is a mismatch.  And if the user doesn't know what a build ID
is, it's a learning opportunity for them, it's quite easy to Google.

Simon


      reply	other threads:[~2020-06-21 11:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 20:42 Philippe Waroquiers
2020-06-20 10:28 ` PING " Philippe Waroquiers
2020-06-20 16:25 ` Pedro Alves
2020-06-21 11:30   ` Philippe Waroquiers
2020-06-21 11:42     ` Simon Marchi [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=ea766da5-c312-7e5b-afae-ebc8285ac1f9@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=philippe.waroquiers@skynet.be \
    /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