From: Pedro Alves <palves@redhat.com>
To: Norbert Lange <nolange79@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][PR build/24805] Explicitly export symbols from gdb_proc_service
Date: Tue, 14 Jan 2020 16:28:00 -0000 [thread overview]
Message-ID: <6cebf642-05a8-585f-2ec8-786d56820371@redhat.com> (raw)
In-Reply-To: <c1a3a253-5b8f-025d-0a3a-a92fe49583a9@redhat.com>
On 1/14/20 3:36 PM, Pedro Alves wrote:
> On 1/6/20 11:39 PM, Norbert Lange wrote:
>> Am Mo., 6. Jan. 2020 um 20:21 Uhr schrieb Pedro Alves <palves@redhat.com>:
>>>
>>> On 1/4/20 8:20 PM, Norbert Lange wrote:
>>>> Compiling GDB with '-fvisibility=hidden' will remove the
>>>> symbols that should be exported.
>>>> This patch explicitly marks them as visible.
>>>
>>> Curious. We have gdb/proc-service.list supposedly for this,
>>> doesn't -Wl,--dynamic-list work with -fvisibility=hidden then?
>>>
>>
>> Obviously it doesn't, else I would not have spent time figuring out
>> why libthread_db wont load.
>
> OK. Haven't looked at visibility issues in years. It also wasn't clear
> to me whether the issue could be that -Wl,--dynamic-list wasn't used
> in your build for some reason, maybe related to how you're configuring GDB.
>
>> -Wl,--dynamic-list merely filters the visible symbols, it does not see
>> "hidden" ones.
>
> BTW, you didn't post an actual patch to the list:
> https://sourceware.org/ml/gdb-patches/2020-01/msg00083.html
I knew I must have been confused. I found your patch on the list,
as a reply to that...
>
> I found it in bugzilla, though.
>
> How about something like this? It's similar to your #2 at
> <https://sourceware.org/bugzilla/show_bug.cgi?id=24805#c3>, but
> I'm using typeof to avoid issues with different systems using
> different prototypes.
BTW, I forgot to mention why I suggested this as alternative
to the push/pop approach. It was that the push/pop approach
makes everything indirectly included by <proc_service.h>
have default visibility too. I don't know whether that ends
up being any function in practice, though.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2020-01-14 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 20:20 Norbert Lange
2020-01-04 20:20 ` [PATCH] always export the symbols for the proc_service interface Norbert Lange
2020-01-06 16:07 ` Tom Tromey
2020-01-06 23:22 ` Norbert Lange
2020-01-06 19:21 ` [PATCH][PR build/24805] Explicitly export symbols from gdb_proc_service Pedro Alves
2020-01-06 23:39 ` Norbert Lange
2020-01-14 15:47 ` Pedro Alves
2020-01-14 16:28 ` Pedro Alves [this message]
2020-01-14 16:57 ` Norbert Lange
2020-01-16 19:56 ` 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=6cebf642-05a8-585f-2ec8-786d56820371@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=nolange79@gmail.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