> Seems this (immediate segfault after program startup, GUI is not coming > up) is caused by gcc-4.0, recompiling with gcc-3.3 makes it work fine > again.
I just installed gcc-4.0.1 on one of my computers and could reproduce the problem there , but it appears to be an optimizer bug in gcc 4.x that trashes the stack. The program works fine when compiled without -O2 there, and valgrind does not complain about my coding either (at least on my regular system with older gcc). I think all I (or Michael as the package maintainer for Debian) could do is modify the configure script so that it refuses to use -O2 when it detects gcc 4.x (in view of this, having -O2 in the default CFLAGS section of Makefile.in no longer looks like a bright idea). Could you please check if removing the "-O2" from the Makefile makes it work for you too, when compiling with gcc-4 ? Thanks, Martin -- Dr. Martin Kroeker [EMAIL PROTECTED] c/o Prof.Dr. Caroline Roehr Institut fuer Anorganische und Analytische Chemie der Universitaet Freiburg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
