From: Pedro Alves <palves@redhat.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Doug Evans <dje@google.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] C++: dlsym casts in gdb/linux-thread-db.c and gdb/gdbserver/thread-db.c
Date: Wed, 05 Aug 2015 13:51:00 -0000 [thread overview]
Message-ID: <55C214E7.6090506@redhat.com> (raw)
In-Reply-To: <20150805133424.7C1181704@oc7340732750.ibm.com>
On 08/05/2015 02:34 PM, Ulrich Weigand wrote:
> Pedro Alves wrote:
>
>> gdb/ChangeLog:
>> 2015-08-03 Pedro Alves <palves@redhat.com>
>>
>> * nat/gdb_thread_db.h (td_init_ftype, td_ta_new_ftype)
>> (td_ta_map_lwp2thr_ftype, td_ta_thr_iter_ftype)
>> (td_ta_event_addr_ftype, td_ta_set_event_ftype)
>> (td_ta_clear_event_ftype, td_ta_event_getmsg_ftype)
>> (td_thr_validate_ftype, td_thr_get_info_ftype)
>> (td_thr_event_enable_ftype, td_thr_tls_get_addr_ftype)
>> (td_thr_tlsbase_ftype, td_symbol_list_ftype, td_ta_delete_ftype):
>> New typedefs.
>
> This breaks the build for me with:
>
> In file included from /home/uweigand/dailybuild/spu-tc-2015-08-04/binutils-gdb-head/binutils-gdb/gdb/gdbserver/thread-db.c:31:
> /home/uweigand/dailybuild/spu-tc-2015-08-04/binutils-gdb-head/binutils-gdb/gdb/gdbserver/../nat/gdb_thread_db.h:20: error: redefinition of typedef ‘td_init_ftype’
> /home/uweigand/dailybuild/spu-tc-2015-08-04/binutils-gdb-head/binutils-gdb/gdb/gdbserver/../nat/gdb_thread_db.h:20: error: previous declaration of ‘td_init_ftype’ was here
> /home/uweigand/dailybuild/spu-tc-2015-08-04/binutils-gdb-head/binutils-gdb/gdb/gdbserver/../nat/gdb_thread_db.h:23: error: redefinition of typedef ‘td_ta_new_ftype’
> /home/uweigand/dailybuild/spu-tc-2015-08-04/binutils-gdb-head/binutils-gdb/gdb/gdbserver/../nat/gdb_thread_db.h:23: error: previous declaration of ‘td_ta_new_ftype’ was here
> [... etc for each of the typedefs ...]
>
> It seems this is caused by the nat/gdb_thread_db.h header file
> being included twice into gdbserver/thread-db.c:
>
> 1) via line 23:
> #include "linux-low.h"
> (which includes "nat/gdb_thread_db.h" at line 20)
>
> 2) directly in line 30:
> #include "nat/gdb_thread_db.h"
>
> and the file not being guarded against double inclusion.
Yeah, I think we should just add the guards.
Are you already taking care of that, or would you like me to?
>
> (I'm not 100% sure whether an identical second typedef is supposed
> to be valid C or not, but at least my GCC 4.1 host compiler rejects
> it in this case.)
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-08-05 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 18:49 [PATCH] " Pedro Alves
2015-08-03 18:54 ` Doug Evans
2015-08-03 19:28 ` [PATCH v2] " Pedro Alves
2015-08-03 19:35 ` Doug Evans
2015-08-04 8:47 ` Pedro Alves
2015-08-05 13:34 ` Ulrich Weigand
2015-08-05 13:51 ` Pedro Alves [this message]
2015-08-05 14:35 ` Ulrich Weigand
2015-08-05 14:36 ` Pedro Alves
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=55C214E7.6090506@redhat.com \
--to=palves@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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