Re: forking heap question

[Havoc Pennington <hp redhat com>]

Edscott Wilson García <edscott imp mx> writes:
> 
>   I was getting random "io X error" after forking and the child was
> not using any GTK, nor was it using exit() in stead of _exit(). I
> finally tracked down the problem to the child using malloc() and
> free(), and overwriting the GTK widget information in the parent
> process. By using stack memory the problem is gone. Is this
> possible? Should the use of heap memory be avoided at all costs when
> using gtk with fork()?

I don't think it's possible. There should be no relation between
parent and child address spaces.

Havoc