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: Simon Burge <simonb%NetBSD.org@localhost>
Date: Wed, 15 Jul 2020 11:10:44 +1000

Kamil Rytarowski wrote:

> On 14.07.2020 06:28, Martin Husemann wrote:
> > 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
> > 
>
> There are many malloc wrappers or replacements for introspection, so
> this should be operational.
>
> We also deliver gnumalloc in base..

I suspect this also doesn't play well with devel/dmalloc then?

Cheers,
Simon.

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

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