hi hi,
I currently fight with some highlevel unit test, that should basically start the
application and immeditely exit.
The Problem I have is that instead of calling gtk_main() I want to init
everything and then shut-down.
The test-framework stats tests with fork to capture crashing.
Before I initialize g_thread and gdk_threads. I wrap lauching the test suite in
gdk_thread_enter/leave().
When the tests run, I often get XLib errors a la
sequence lost (0x100b9 > 0xb9) in reply to 0x0!
...
To me this sounds like probelm in message passing. Should I add another
gdk_thread_enter/leave() after the fork (for each test case)?
Does anyone do unit test that test the GUI?
Stefan
--
\|/ Stefan Kost
<@ @> private business
+-oOO-(_)-OOo------------------------------------------------------ - - - - -
| __ Address Simildenstr. 5 HTWK Leipzig, Fb IMN, Postfach 301166
| /// 04277 Leipzig 04251 Leipzig
| __ /// Germany Germany
| \\\/// Phone +49341 2253538 +49341 30766101
| \__/ EMail st_kost_at_gmx.net kost_at_imn.htwk-leipzig.de
| WWW www.sonicpulse.de www.imn.htwk-leipzig.de/~kost/about.html
===-=-=--=---=---------------------------------- - - - - -
_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
