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

To: current-users%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: christos%astron.com@localhost (Christos Zoulas)
Date: Thu, 16 Jul 2020 14:40:09 -0000 (UTC)

In article <7171.1594774550%splode.eterna.com.au@localhost>,
matthew green  <mrg%eterna.com.au@localhost> wrote:
>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.

I fixed it by adding the 3 functions to tc.alloc.c both in pkgsrc and
upstream.

christos

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

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

Prev by Date: daily CVS update output
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