From: Tom de Vries <tdevries@suse.de>
To: Christian Biesinger <cbiesinger@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: [PATCH][gdbserver] Add missing include of gdbsupport/agent.h
Date: Thu, 18 Jun 2020 10:44:46 +0200 [thread overview]
Message-ID: <131a6f7c-26f1-1012-32e3-2582e3c6d7f8@suse.de> (raw)
In-Reply-To: <1bc315c0-55e6-08bf-8aa3-e0e30bba2c81@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
[ was: Re: [committed][gdbserver] Fix Wlto-type-mismatch for debug_agent ]
On 6/17/20 6:38 PM, Tom de Vries wrote:
> On 6/12/20 8:19 PM, Christian Biesinger wrote:
>> On Fri, Jun 12, 2020 at 11:37 AM Tom de Vries <tdevries@suse.de> wrote:
>>>
>>> Hi,
>>>
>>> When building gdb including gdbserver with CFLAGS/CXXFLAGS -O2 -g -flto=auto,
>>> I run into:
>>> ...
>>> src/gdbserver/../gdbsupport/agent.h:47:13: error: type of 'debug_agent' \
>>> does not match original declaration [-Werror=lto-type-mismatch]
>>> extern bool debug_agent;
>>> ^
>>> src/gdbserver/ax.cc:28:5: note: type 'int' should match type 'bool'
>>> int debug_agent = 0;
>>> ^
>>> src/gdbserver/ax.cc:28:5: note: 'debug_agent' was previously declared here
>>> src/gdbserver/ax.cc:28:5: note: code may be misoptimized unless \
>>> -fno-strict-aliasing is used
>>
>> So it sounds like this didn't come up before because ax.cc doesn't
>> include gdbsupport/agent.h?
>
> Yes.
>
>> It probably should?
>
> Um, good point, thanks.
>
> Though ax.h does:
> ...
> #ifdef IN_PROCESS_AGENT
> #define debug_threads debug_agent
> #endif
> ...
> so I wonder if we should have the include there instead. I'll try to
> test this.
Any comments?
Thanks,
- Tom
[-- Attachment #2: 0001-gdbserver-Add-missing-include-of-gdbsupport-agent.h.patch --]
[-- Type: text/x-patch, Size: 1263 bytes --]
[gdbserver] Add missing include of gdbsupport/agent.h
The file gdbserver/ax.h contains:
...
#ifdef IN_PROCESS_AGENT
#define debug_threads debug_agent
#endif
...
but does not declare debug_agent.
Fix this by adding an include of gdbsupport/agent.h.
[ If this fix would have been in place before commit 8118159c69 "[gdbserver] Fix
Wlto-type-mismatch for debug_agent", we would have simply run into this build
breaker with a regular, non-lto build:
...
src/gdbserver/ax.cc:28:5: error: conflicting declaration 'int debug_agent'
int debug_agent = 0;
^~~~~~~~~~~
In file included from src/gdbserver/ax.h:25:0,
from src/gdbserver/ax.cc:20:
src/gdbsupport/agent.h:47:13: note: previous declaration as 'bool debug_agent'
extern bool debug_agent;
^~~~~~~~~~~
... ]
Tested on x86_64-linux.
gdbserver/ChangeLog:
2020-06-18 Tom de Vries <tdevries@suse.de>
* ax.h: Include gdbsupport/debug_agent.h.
---
gdbserver/ax.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/gdbserver/ax.h b/gdbserver/ax.h
index 1fba69e7ad..b7ff7d8910 100644
--- a/gdbserver/ax.h
+++ b/gdbserver/ax.h
@@ -22,6 +22,7 @@
#include "regcache.h"
#ifdef IN_PROCESS_AGENT
+#include "gdbsupport/agent.h"
#define debug_threads debug_agent
#endif
next prev parent reply other threads:[~2020-06-18 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 16:37 [committed][gdbserver] Fix Wlto-type-mismatch for debug_agent Tom de Vries
2020-06-12 18:19 ` Christian Biesinger
2020-06-17 16:38 ` Tom de Vries
2020-06-18 8:44 ` Tom de Vries [this message]
2020-06-19 20:22 ` [PATCH][gdbserver] Add missing include of gdbsupport/agent.h Christian Biesinger
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=131a6f7c-26f1-1012-32e3-2582e3c6d7f8@suse.de \
--to=tdevries@suse.de \
--cc=cbiesinger@google.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