Re: recent changes to pthread_fork.c:fork() cause static linking to fail if the app provides its own malloc()

To: NetBSD-current Users's Discussion List <current-users%netbsd.org@localhost>, NetBSD User-Level Technical Discussion List <tech-userlevel%NetBSD.org@localhost>
Subject: Re: recent changes to pthread_fork.c:fork() cause static linking to fail if the app provides its own malloc()
From: Joerg Sonnenberger <joerg%bec.de@localhost>
Date: Tue, 14 Jul 2020 00:28:46 +0200

On Mon, Jul 13, 2020 at 03:05:17PM -0700, Greg A. Woods wrote:
> I think it is the following change (and perhaps more similar/related
> changes) which breaks static linking of applications which wish to
> supply their own implementation of malloc(), and which call, e.g.,
> fork():

I consider it a strong WONTFIX. It's no different from not poviding
posix_memalign etc.

Joerg

Follow-Ups:
- Re: recent changes to pthread_fork.c:fork() cause static linking to fail if the app provides its own malloc()
  - From: Greg A. Woods

References:
- recent changes to pthread_fork.c:fork() cause static linking to fail if the app provides its own malloc()
  - From: Greg A. Woods

Prev by Date: recent changes to pthread_fork.c:fork() cause static linking to fail if the app provides its own malloc()
Next by Date: Re: recent changes to pthread_fork.c:fork() cause static linking to fail if the app provides its own malloc()
Previous by Thread: recent changes to pthread_fork.c:fork() cause static linking to fail if the app provides its own malloc()
Next by Thread: Re: recent changes to pthread_fork.c:fork() cause static linking to fail if the app provides its own malloc()
Indexes:

Home | Main Index | Thread Index | Old Index