public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Björn Schäpers" <gcc@hazardy.de>
To: Eli Zaretskii <eliz@gnu.org>, Ian Lance Taylor <iant@google.com>
Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: [PATCH 6/4] libbacktrace: Add loaded dlls after initialize
Date: Mon, 29 Jul 2024 21:41:07 +0200	[thread overview]
Message-ID: <dfabf822-9a1e-4f17-a8d0-c545552fa2ee@hazardy.de> (raw)
In-Reply-To: <865xsoytat.fsf@gnu.org>

Am 29.07.2024 um 19:58 schrieb Eli Zaretskii:
>> From: Ian Lance Taylor <iant@google.com>
>> Date: Mon, 29 Jul 2024 09:46:46 -0700
>> Cc: Eli Zaretskii <eliz@gnu.org>, gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
>>
>> On Fri, Mar 15, 2024 at 1:41 PM Björn Schäpers <gcc@hazardy.de> wrote:
>>>
>>> Am 10.01.2024 um 13:34 schrieb Eli Zaretskii:
>>>>> Date: Tue, 9 Jan 2024 21:02:44 +0100
>>>>> Cc: iant@google.com, gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
>>>>> From: Björn Schäpers <gcc@hazardy.de>
>>>>>
>>>>> Am 07.01.2024 um 18:03 schrieb Eli Zaretskii:
>>>>>> In that case, you an call either GetModuleHandeExA or
>>>>>> GetModuleHandeExW, the difference is minor.
>>>>>
>>>>> Here an updated version without relying on TEXT or TCHAR, directly calling
>>>>> GetModuleHandleExW.
>>>>
>>>> Thanks, this LGTM (but I couldn't test it, I just looked at the
>>>> sour ce code).
>>>
>>> Here an updated version. It is rebased on the combined approach of getting the
>>> loaded DLLs and two minor changes to suppress warnings.
>>
>> This bug report was filed about this patch:
>>
>> https://github.com/ianlancetaylor/libbacktrace/issues/131
>>
>>> src\pecoff.c(86): error C2059: syntax error: '('
>>> src\pecoff.c(89): error C2059: syntax error: '('
>>>
>>> It works fine if deleting CALLBACK and NTAPI.
>>
>> Any ideas?
> 
> Instead of deleting those, move them inside the parentheses:
> 
> typedef VOID (CALLBACK *LDR_DLL_NOTIFICATION)(ULONG,
> 					      struct dll_notification_data*,
> 					      PVOID);
> typedef NTSTATUS (NTAPI *LDR_REGISTER_FUNCTION)(ULONG,
> 						LDR_DLL_NOTIFICATION, PVOID,
> 						PVOID*);
> 
> and also I think you need to include <ntdef.h>, for the definition
> of the NTSTATUS type.
> 
> Caveat: I don't have MSVC, so I couldn't verify that these measures
> fix the problem, sorry.

Moving into the parentheses does fix the issue: https://godbolt.org/z/Pe558ofYz

NTSTATUS is typedefed directly before, so that no additional include is needed.

  reply	other threads:[~2024-07-29 19:41 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 10:54 [PATCH 1/4] libbacktrace: change all pc related variables to uintptr_t Björn Schäpers
2023-01-20 10:54 ` [PATCH 2/4] libbacktrace: detect executable path on windows Björn Schäpers
2023-01-23 23:00   ` Ian Lance Taylor
2023-01-24 13:11     ` Eli Zaretskii
2023-01-24 14:35       ` Ian Lance Taylor
2023-01-24 16:52         ` Eli Zaretskii
2023-01-24 17:58           ` Ian Lance Taylor
2023-01-24 18:11             ` Eli Zaretskii
2023-01-24 18:32               ` Ian Lance Taylor
2023-02-05  9:20                 ` Björn Schäpers
2023-02-06  0:22                   ` Ian Lance Taylor
2023-11-20 19:56                     ` Björn Schäpers
2023-11-29 22:05                       ` Ian Lance Taylor
2023-01-24 21:00           ` Björn Schäpers
2023-01-20 10:54 ` [PATCH 3/4] libbacktrace: work with aslr " Björn Schäpers
2023-01-20 13:39   ` Eli Zaretskii
2023-01-20 16:46     ` Gabriel Ravier
2023-01-20 19:19       ` Eli Zaretskii
2023-01-20 20:39         ` Gabriel Ravier
2023-01-21  4:05           ` Eli Zaretskii
2023-01-21  9:18             ` LIU Hao
2023-01-21  9:25               ` Eli Zaretskii
2023-01-21 10:47             ` Gabriel Ravier
2023-01-21 11:42               ` Eli Zaretskii
2023-11-20 19:57                 ` Björn Schäpers
2023-11-20 20:07                   ` Eli Zaretskii
2023-11-21 19:35                     ` Björn Schäpers
2023-11-22  1:13                       ` LIU Hao
2023-11-30 19:25                   ` Ian Lance Taylor
2023-01-20 10:54 ` [PATCH 4/4] libbacktrace: get debug information for loaded dlls Björn Schäpers
2023-11-30 19:53   ` Ian Lance Taylor
2023-11-30 20:16     ` Eli Zaretskii
2024-01-02 23:12     ` Björn Schäpers
2024-01-04 22:33       ` [PATCH 5/4] libbacktrace: improve getting " Björn Schäpers
2024-01-06 22:15         ` [PATCH 6/4] libbacktrace: Add loaded dlls after initialize Björn Schäpers
2024-01-07  6:50           ` Eli Zaretskii
     [not found]             ` <4cb3a2a5-c0b3-40c8-b460-f21d65a9aea2@hazardy.de>
2024-01-07 14:46               ` Eli Zaretskii
2024-01-07 16:07                 ` Björn Schäpers
2024-01-07 17:03                   ` Eli Zaretskii
2024-01-09 20:02                     ` Björn Schäpers
2024-01-10 12:34                       ` Eli Zaretskii
2024-03-15 20:41                         ` Björn Schäpers
2024-07-29 16:46                           ` Ian Lance Taylor
2024-07-29 17:58                             ` Eli Zaretskii
2024-07-29 19:41                               ` Björn Schäpers [this message]
2024-07-30 16:28                                 ` Ian Lance Taylor
2024-01-23 22:37         ` [PATCH 5/4] libbacktrace: improve getting debug information for loaded dlls Ian Lance Taylor
2024-01-25 19:53           ` Björn Schäpers
2024-01-25 22:04             ` Ian Lance Taylor
2024-03-15 20:40               ` Björn Schäpers
2024-04-25 20:14                 ` Björn Schäpers
2024-04-28 18:16                   ` Ian Lance Taylor
2024-05-02 19:23                     ` Björn Schäpers
2024-05-03 22:27                       ` Ian Lance Taylor
2024-01-23 21:24       ` [PATCH 4/4] libbacktrace: get " Björn Schäpers
2023-01-20 22:25 ` [PATCH 1/4] libbacktrace: change all pc related variables to uintptr_t Ian Lance Taylor
2023-01-23 20:17   ` Björn Schäpers

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=dfabf822-9a1e-4f17-a8d0-c545552fa2ee@hazardy.de \
    --to=gcc@hazardy.de \
    --cc=eliz@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.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).