Surely you must be able to fork in a GTK program, since this is used in
the GNOME libraries for things like scores, program loading and other
things (the best example being the panel, where fork'ing and exec'ing are
its main job.
Do you know which process is dieing? Also, what happens if you run your
script like this:
$ gdb python
(gdb copyright message)
gdb> run scriptname.py
Which of the two processes dies? If the main process dies, could you try
doing a backtrace (with the bt command under gdb), and see if it gives any
clues.
James Henstridge
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Mon, 30 Nov 1998, Martin Preishuber wrote:
> James Henstridge wrote:
>
> > That is wierd. When you import GTK, it creates a connection to the X
> > server. I guess when the fork occurs, both programs have fd's for the
> > same connection to the X server.
>
> understandable ...
>
> > Do you get the same error if you perform the fork before importing gtk?
>
> it just happens when I import gtk.
>
> does that mean, I can't fork within any python script which uses gtk ?
>
> Martin
>
> --
> Martin Preishuber - Student, ECLiPt Member, SysAdmin
> http://eclipt.uni-klu.ac.at,
> mailto:[EMAIL PROTECTED]
>
> The difference between legal separation and divorce is that legal
> separation gives the man time to hide his money.
> To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
>
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
