public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite/README: update default value of INTERNAL_GDBFLAGS
Date: Sat, 19 Feb 2022 23:09:10 -0500	[thread overview]
Message-ID: <ED667473-04F7-430E-B935-E6A909E706EA@gmail.com> (raw)
In-Reply-To: <46f0e775-0904-092d-93dd-df263fbd28d7@polymtl.ca>

Hi Simon,

> Le 19 févr. 2022 à 20:41, Simon Marchi <simon.marchi@polymtl.ca> a écrit :
> 
>> On 2022-02-19 18:40, Philippe Blain via Gdb-patches wrote:
>> The INTERNAL_GDBFLAGS runtest variable was updated in 55c3ad88013
>> ([gdb/testsuite] Prevent pagination in GDB_INTERNALFLAGS, 2020-10-26) to
>> disable pagination, and in aae1c79a03a (PR python/12227..., 2010-12-07)
>> to point to the data directory, but its default value mentioned in the
>> testsuite's README was not kept up to date.
>> 
>> Update the README accordingly, and mention where the default value is
>> set, so that it's easier for futur new contributors to check if the
>> default mentioned in the README is still current.
>> ---
>> 
>> Notes:
>>    I noticed that while testing the fix for PR 24069, since I wanted
>>    to use my '~/.gdbinit' with 'set startup-with-shell off' for all tests,
>>    and found out that setting INTERNAL_GDBFLAGS to only '-nw' made some things
>>    a little worse (as GDB was then missing '-data-directory').
>> 
>>    Meta note: when I sent this patch earlier (and messed-up my CCs) in [1], I was
>>    confused by the fact that my CCs for Simon, Doug Evans and Tom de Vries were
>>    not showing up on public-inbox, even in the "raw" view [2]. After a little
>>    web search I think this is due to them setting the mailman "avoid duplicates"
>>    setting [3].
>> 
>>    [1] https://pi.simark.ca/gdb-patches/20220219212442.18136-1-levraiphilippeblain@gmail.com/T/#u
>>    [2] https://pi.simark.ca/gdb-patches/20220219212442.18136-1-levraiphilippeblain@gmail.com/raw
>>    [3] https://wiki.list.org/DOC/Mailman%202.1%20Members%20Manual#A7.2_How_can_I_avoid_getting_duplicate_messages.3F_.28duplicates_option.29
>> 
>> gdb/testsuite/README | 10 ++++++++--
>> 1 file changed, 8 insertions(+), 2 deletions(-)
>> 
>> diff --git a/gdb/testsuite/README b/gdb/testsuite/README
>> index 7552774c78b..2d3f1c45966 100644
>> --- a/gdb/testsuite/README
>> +++ b/gdb/testsuite/README
>> @@ -168,11 +168,14 @@ INTERNAL_GDBFLAGS
>> 
>> Command line options passed to all GDB invocations.
>> 
>> -The default is "-nw -nx".
>> +The default is set in lib/gdb.exp and is currently
>> +"-nw -nx -data-directory /path/to/build/directory/gdb/data-directory -iex 'set height 0' -iex 'set width 0'".
>> 
>> `-nw' disables any of the windowed interfaces.
>> `-nx' disables ~/.gdbinit, so that it doesn't interfere with
>> the tests.
>> +`-data-directory` points the the data directory in the build directory
>> +`-iex 'set {height,width} 0'` disables pagination
> 
> I think this should just say "see the default in lib/gdb.exp", and the
> flags can be explained there.  That would avoid things getting out of
> sync.

Yes, you are probably right. I can send an updated patch with that change. 

Philippe. 

  reply	other threads:[~2022-02-20  4:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19 23:40 Philippe Blain
2022-02-20  1:41 ` Simon Marchi
2022-02-20  4:09   ` Philippe Blain [this message]
2022-02-20 16:49 ` [PATCH v2] gdb/testsuite/README: point to " Philippe Blain
2022-02-22 13:46   ` Simon Marchi
2022-02-22 14:01     ` Philippe Blain
2022-02-22 14:31       ` Simon Marchi
2022-02-22 14:45         ` Philippe Blain
2022-02-22 14:46           ` 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=ED667473-04F7-430E-B935-E6A909E706EA@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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).