From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
gdb-patches@sourceware.org, thomas@schwinge.name
Subject: Re: [PATCH] hurd: Fix RPC link names
Date: Mon, 31 Jan 2022 20:31:22 -0500 [thread overview]
Message-ID: <48fd3788-7943-6576-3918-748508e26c43@polymtl.ca> (raw)
In-Reply-To: <20220201012313.kvhplo47mk5fe3ch@begin>
On 2022-01-31 20:23, Samuel Thibault wrote:
> Simon Marchi, le lun. 31 janv. 2022 20:05:53 -0500, a ecrit:
>>
>>
>> On 2022-01-31 20:05, Samuel Thibault wrote:
>>> Simon Marchi, le lun. 31 janv. 2022 19:56:35 -0500, a ecrit:
>>>> On 2022-01-31 19:04, Samuel Thibault via Gdb-patches wrote:
>>>>> The RPC stub code expects to be calling a C function, not a C++
>>>>> function.
>>>>>
>>>>> diff --git a/gdb/gnu-nat.c b/gdb/gnu-nat.c
>>>>> index 67ce00e9c30..030ccf01d68 100644
>>>>> --- a/gdb/gnu-nat.c
>>>>> +++ b/gdb/gnu-nat.c
>>>>> @@ -1766,11 +1766,13 @@ do_mach_notify_dead_name (mach_port_t notify, mach_port_t dead_port)
>>>>>
>>>>> \f
>>>>> #define ILL_RPC(fun, ...) \
>>>>> + extern "C" { \
>>>>> extern kern_return_t fun (__VA_ARGS__); \
>>>>
>>>> I think this could be on a single line:
>>>>
>>>> extern "C" kern_return_t fun..
>>>
>>> Ah right here is a simplified version.
>>>
>>> Samuel
>>>
>>>
>>> The RPC stub code expects to be calling a C function, not a C++
>>> function.
>>>
>>> diff --git a/gdb/gnu-nat.c b/gdb/gnu-nat.c
>>> index e0219b1a3ff..81676308882 100644
>>> --- a/gdb/gnu-nat.c
>>> +++ b/gdb/gnu-nat.c
>>> @@ -1766,7 +1766,7 @@ do_mach_notify_dead_name (mach_port_t notify, mach_port_t dead_port)
>>>
>>> \f
>>> #define ILL_RPC(fun, ...) \
>>> - extern kern_return_t fun (__VA_ARGS__); \
>>> + extern "C" kern_return_t fun (__VA_ARGS__); \
>>> kern_return_t fun (__VA_ARGS__) \
>>> { \
>>> warning (_("illegal rpc: %s"), #fun); \
>>
>> Thanks, this is OK to push.
>
> (I don't have commit access)
>
> Samuel
Oh, sorry! Pushed it for you.
Simon
next prev parent reply other threads:[~2022-02-01 1:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 0:04 Samuel Thibault via Gdb-patches
2022-02-01 0:56 ` Simon Marchi via Gdb-patches
2022-02-01 1:05 ` Samuel Thibault via Gdb-patches
2022-02-01 1:05 ` Simon Marchi via Gdb-patches
2022-02-01 1:23 ` Samuel Thibault via Gdb-patches
2022-02-01 1:31 ` Simon Marchi via Gdb-patches [this message]
2022-02-01 2:08 ` Samuel Thibault via Gdb-patches
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=48fd3788-7943-6576-3918-748508e26c43@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=samuel.thibault@gnu.org \
--cc=simon.marchi@polymtl.ca \
--cc=thomas@codesourcery.com \
--cc=thomas@schwinge.name \
/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