From: Simon Marchi <simark@simark.ca>
To: Jonah Graham <jonah@kichwacoders.com>,
Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>,
Iain Buclaw <ibuclaw@gdcproject.org>,
Nick Alcock <nick.alcock@oracle.com>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: Propose we release GDB 9.1 next weekend (Feb 01-02)
Date: Sat, 01 Feb 2020 15:45:00 -0000 [thread overview]
Message-ID: <3e5c6bc8-30f5-3c6f-b301-1153a6cf9416@simark.ca> (raw)
In-Reply-To: <CAPmGMvhOazCaTg66qQBqyZUEbiP0bo_ummMPRth0HvXU+AfWng@mail.gmail.com>
On 2020-02-01 7:57 a.m., Jonah Graham wrote:
> Can fullname field (at least in MI output) continue to be
> realpath_fullname concept and if needed in MI a new field added for
> absolute_fullname? In the CLI output users see just file
> (../src/main2.c), but that is not generally useful in the IDE case as
> it is display only.
The MI documentation doesn't say anything about what that fullname field should
contain, in fact it's just shown in examples and never formally described.
But given that it has contained the realpath for years, this is what the IDEs/users
expect, so I indeed think we should make sure it stays that way.
> Tom If you decide to revert (which would be my preference) I will
> happily work with you to get this back in. I previously wrote a
> testcase for the simple case that did already get fixed, I can work on
> a testcase for the new case too for the suite if it helps.
> https://sourceware.org/ml/gdb-patches/2019-08/msg00421.html
Thanks, that will be useful.
Simon
next prev parent reply other threads:[~2020-02-01 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 15:41 Joel Brobecker
2020-01-26 16:07 ` Eli Zaretskii
2020-01-28 16:43 ` Nick Alcock
2020-01-28 17:06 ` Hannes Domani via gdb-patches
[not found] ` <ee83b6c0-8e18-eb1e-18c8-f9df79b547d7@simark.ca>
2020-01-28 17:37 ` Hannes Domani via gdb-patches
2020-02-01 3:20 ` Jonah Graham
2020-02-01 8:00 ` Simon Marchi
2020-02-01 12:17 ` Joel Brobecker
2020-02-01 12:58 ` Jonah Graham
2020-02-01 13:06 ` Joel Brobecker
2020-02-05 10:08 ` Tom Tromey
2020-02-01 15:45 ` Simon Marchi [this message]
2020-02-01 15:37 ` Simon Marchi
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=3e5c6bc8-30f5-3c6f-b301-1153a6cf9416@simark.ca \
--to=simark@simark.ca \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.org \
--cc=jonah@kichwacoders.com \
--cc=nick.alcock@oracle.com \
--cc=palves@redhat.com \
--cc=tom@tromey.com \
/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