From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb: add setting to disable reading source code files
Date: Thu, 23 Sep 2021 14:27:29 -0600 [thread overview]
Message-ID: <877df73umm.fsf@tromey.com> (raw)
In-Reply-To: <9b4e2c9c4e0c4153cda06ccb075e49b529253413.1631136815.git.andrew.burgess@embecosm.com> (Andrew Burgess's message of "Wed, 8 Sep 2021 22:34:55 +0100")
>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:
Andrew> In some situations it is possible that a user might not want GDB to
Andrew> try and access source code files, for example, the source code might
Andrew> be stored on a slow to access network file system.
[...]
Looks good to me.
Tom
next prev parent reply other threads:[~2021-09-23 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 21:34 [PATCH 0/2] New option to switch off source code display Andrew Burgess
2021-09-08 21:34 ` [PATCH 1/2] gdb: remove duplicate cmd_list_element declarations Andrew Burgess
2021-09-23 20:21 ` Tom Tromey
2021-09-08 21:34 ` [PATCH 2/2] gdb: add setting to disable reading source code files Andrew Burgess
2021-09-09 18:51 ` Philippe Waroquiers
2021-09-23 20:27 ` Tom Tromey [this message]
2021-09-24 16:14 ` Pedro Alves
2021-09-27 10:33 ` Andrew Burgess
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=877df73umm.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@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).