public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Enze Li <enze.li@hotmail.com>, gdb-patches@sourceware.org
Cc: enze.li@gmx.com
Subject: Re: [PATCH] gdb: fix -Wdeprecated-declarations on macOS
Date: Tue, 28 Mar 2023 10:55:32 -0400	[thread overview]
Message-ID: <6379554d-4e45-0ff8-a972-47596ea83b90@simark.ca> (raw)
In-Reply-To: <OS3P286MB2152EBC805B1484BE3970863F0889@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM>

On 3/28/23 10:16, Enze Li via Gdb-patches wrote:
> I noticed that there are some issues when compiling on macOS.  There are
> a few places where errors like the following are reported,
> 
> ======
>   CXX    cli/cli-cmds.o
> cli/cli-cmds.c:929:14: error: 'vfork' is deprecated: Use posix_spawn or fork [-Werror,-Wdeprecated-declarations]
>   if ((pid = vfork ()) == 0)
>              ^
> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/unistd.h:604:1: note: 'vfork' has been explicitly marked deprecated here
> __deprecated_msg("Use posix_spawn or fork")
> ^
> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:208:48: note: expanded from macro '__deprecated_msg'
>         #define __deprecated_msg(_msg) __attribute__((__deprecated__(_msg)))
>                                                       ^
> 1 error generated.
> ======
> 
> This patch is only available for the macOS platform.  This is done by
> using macros to differentiate between specific platforms.
> 
> Tested by rebuilding both on x86_64 linux and macOS Big Sur.

Any idea why vfork is deprecated on macOS?  I can't find any answer
online.

I think it would be good to have a gdb_ util function with the ifdef at
a single place, with an appropriate comment.  I don't know how to call
this function though.  Would calling it gdb_vfork be misleading, because
it won't always vfork?

Simon

  reply	other threads:[~2023-03-28 14:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 14:16 Enze Li
2023-03-28 14:55 ` Simon Marchi [this message]
2023-03-28 15:10   ` John Baldwin
2023-03-28 15:57     ` Tom Tromey
2023-03-28 16:01     ` Simon Marchi
2023-03-28 17:52       ` John Baldwin
2023-03-28 17:57         ` John Baldwin

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=6379554d-4e45-0ff8-a972-47596ea83b90@simark.ca \
    --to=simark@simark.ca \
    --cc=enze.li@gmx.com \
    --cc=enze.li@hotmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).