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

To: Martin Husemann <martin%duskware.de@localhost>
Subject: re: recent changes to pthread_fork.c:fork() cause static linking to fail if the app provides its own malloc()
From: matthew green <mrg%eterna.com.au@localhost>
Date: Wed, 15 Jul 2020 10:55:50 +1000

Martin Husemann writes:
> 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?

it was, yes.  i worked around it a few days ago.


.mrg.

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

Prev by Date: Re: 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: 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