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: Martin Husemann <martin%duskware.de@localhost>
Date: Tue, 14 Jul 2020 06:28:50 +0200

On Tue, Jul 14, 2020 at 02:49:00AM +0200, Joerg Sonnenberger wrote:
> Replacing malloc is just as invalid from a strict standard compliance
> perspective, so *shrug*

Why is that?

We have e.g. shells/standalone-tcsh that does it. Is it broken now?

Martin

Follow-Ups:
- re: recent changes to pthread_fork.c:fork() cause static linking to fail if the app provides its own malloc()
  - From: matthew green
- Re: recent changes to pthread_fork.c:fork() cause static linking to fail if the app provides its own malloc()
  - From: Kamil Rytarowski

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

Prev by Date: daily CVS update output
Next by Date: rump bridge fun
Previous by Thread: Re: 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