forking heap question



Hi,

  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()? 

  Thanks in advance for any clue to this puzzling dilema.


Edscott Wilson Garcia



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]