Here is the output:

[mclasen@planemask Gui]$ /usr/libexec/vino-server >&~/LOG
*** buffer overflow detected ***: /usr/libexec/vino-server terminated
======= Backtrace: =========
/lib64/libc.so.6(__fortify_fail+0x37)[0x3ac20f7537]
/lib64/libc.so.6[0x3ac20f5590]
/lib64/libc.so.6[0x3ac20f6d77]
/usr/libexec/vino-server[0x415d5e]
/usr/libexec/vino-server[0x40f7ad]
/lib64/libgobject-2.0.so.0[0x3527c1134d]
/lib64/libgobject-2.0.so.0(g_object_newv+0x296)[0x3527c11cb6]
/lib64/libgobject-2.0.so.0(g_object_new_valist+0x241)[0x3527c12721]
/lib64/libgobject-2.0.so.0(g_object_new+0xcc)[0x3527c1298c]
/usr/libexec/vino-server[0x40cebe]
/usr/libexec/vino-server[0x40b8a5]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x3ac201ea2d]
/usr/libexec/vino-server[0x408469]


Rebuilding with -O0 makes this go away. 

I'm a bit puzzled, since the code looks fine to me:


in server/libvncserver/rfb/rfb.h, in the _rfbScreenInfo struct:

    char rfbThisHost[255];

...and in server/libvncserver/main.c:

   rfbScreen=malloc(sizeof(rfbScreenInfo));

   [...]

   gethostname(rfbScreen->rfbThisHost, 255);


gcc problem ?