public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simon.marchi@polymtl.ca>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] gdb/tui: cleanup includes
Date: Mon, 10 Jun 2024 10:44:27 +0200	[thread overview]
Message-ID: <a15fce96-d11a-4192-82fa-15142c1e9512@suse.de> (raw)
In-Reply-To: <36c719ba-a224-46ff-8e03-d6a2e93e79fa@polymtl.ca>

On 6/9/24 16:14, Simon Marchi wrote:
> 
> 
> On 2024-06-08 06:14, Tom de Vries wrote:
>> On 6/3/24 16:57, Tom Tromey wrote:
>>>>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
>>>
>>> Simon> Remove includes reported as unused by clangd.  Then, add any includes
>>> Simon> necessary to get rid of errors (includes possibly relying on previous
>>> Simon> includes)..
>>>
>>> Simon> I didn't remove the includes of gdb-safe-ctypes.h, because it appears to
>>> Simon> do some some preprocessor magic, redefining standard macros.  I'm afraid
>>> Simon> that removing these includes could change the behavior unintentionally.
>>>
>>> It's never been super clear when gdb should use the libiberty stuff and
>>> when it should not.
>>>
>>> Approved-By: Tom Tromey <tom@tromey.com>
>>
>> This commit introduced a regression for me:
>> ...
>> Running /data/vries/gdb/src/gdb/testsuite/gdb.python/tui-window.exp ...
>> WARNING: timeout in accept_gdb_output
>> WARNING: timeout in accept_gdb_output
>> FAIL: gdb.python/tui-window.exp: Window was updated
>> ...
>>
>> Filed here (  https://sourceware.org/bugzilla/show_bug.cgi?id=31865 ) with gdb.log attached.
>>
>> Thanks,
>> - Tom
>>
> 
> Sorry, I messed up. See the patch here:
> 
> https://inbox.sourceware.org/gdb-patches/20240609141034.238889-1-simon.marchi@polymtl.ca/T/#u
> 
> I'm currently on leave and won't necessarily be near a computer all day, so if you think this
> patch is ok, feel free to push it on my behalf in order to fix the build as quickly as possible.
> 

Thanks for the quick fix, pushed.

- Tom


  reply	other threads:[~2024-06-10  8:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31  2:54 [PATCH 1/3] gdb/tui: change some macros to functions Simon Marchi
2024-05-31  2:54 ` [PATCH 2/3] gdb: add IWYU export pragams to gdb_curses.h Simon Marchi
2024-06-03 14:56   ` Tom Tromey
2024-06-08  3:07     ` Simon Marchi
2024-05-31  2:54 ` [PATCH 3/3] gdb/tui: cleanup includes Simon Marchi
2024-06-03 14:57   ` Tom Tromey
2024-06-08 10:14     ` Tom de Vries
2024-06-09 14:14       ` Simon Marchi
2024-06-10  8:44         ` Tom de Vries [this message]
2024-06-12  4:29           ` Aditya Kamath1
2024-06-09  5:51     ` Aditya Kamath1
2024-06-03 14:55 ` [PATCH 1/3] gdb/tui: change some macros to functions Tom Tromey

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=a15fce96-d11a-4192-82fa-15142c1e9512@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).