Re: segmentation fault while using thread and gtk2

[SuicideJunkie]

What is it you're trying to do there?

Bad things tend to happen if you try to mix threads and Tk.

A much safer way to go about it is to start your threads up front and keep them isolated from each other. Have one thread which does all of the GUI & Tk stuff. Have another thread (or thread pool) for doing background processing. Only the single GUI thread should ever touch the Tk elements, and the processing threads should pass their results to the GUI thread (eg: via shared memory) and let it draw the results.

Don't spawn new threads from the GUI thread, and definitely don't do it after you have started creating Tk elements unless you like coding in the Twilight Zone.

PS: The word you're looking for is segmentation, not sigmentation. Searches won't work very well that way.

[Muskovitz]

do you mean that i must execute a thread before those Gtk2 codes but what i am trying to do is when that button clicked a thread will start and execute!

[Anonymous Monk]

For the pattern and other tips see Re: Win32::GUI window freezing, even with threading., Re: Win32::GUI window freezing, even with threading. (win32-gui-tk-thread-dequeue.pl, Thread::Queue::popnow/push),

can't share Tk mainwondow between threads, Re^3: Threads and TCL DeleteInterpProc, Re^3: Using MCE to write to multiple files. with commentary on the complexity at Re^4: Using MCE to write to multiple files.

for more stuff to sift through see ?node_id=3989;BIT=use%20thread%3BTk;BIS=%3B;a=%5BAnonymous%20Monk%5D%5Bzentara%5D%5BBrowserUk%5D

Maybe simply adding

Glib::Object->set_threadsafe (1);

use Gtk2 qw/-init -threads-init/;

could make your program magically work ... its better strategy to have a gui thread and a background worker thread