Bug 506099 - vino-server aborts on startup
vino-server aborts on startup
Product: Fedora
Classification: Fedora
Component: gcc (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Fedora Extras Quality Assurance
: 505574 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2009-06-15 11:12 EDT by Matthias Clasen
Modified: 2009-06-19 09:24 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-06-16 08:46:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
preprocessor output of the file in question (139.13 KB, text/plain)
2009-06-15 11:50 EDT, Matthias Clasen
no flags Details

  None (edit)
Description Matthias Clasen 2009-06-15 11:12:07 EDT
Here is the output:

[mclasen@planemask Gui]$ /usr/libexec/vino-server >&~/LOG
*** buffer overflow detected ***: /usr/libexec/vino-server terminated
======= Backtrace: =========

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:



   gethostname(rfbScreen->rfbThisHost, 255);

gcc problem ?
Comment 1 Matthias Clasen 2009-06-15 11:50:16 EDT
Created attachment 347956 [details]
preprocessor output of the file in question
Comment 3 Jakub Jelinek 2009-06-16 08:46:45 EDT
Should be fixed in gcc-4.4.0-9.  Packages that were built with gcc-4.4.0-{7,8} and hit this bug need to be rebuilt.
Comment 4 Caolan McNamara 2009-06-17 10:34:29 EDT
*** Bug 505574 has been marked as a duplicate of this bug. ***
Comment 5 Sami Farin 2009-06-19 05:16:58 EDT
vim-7.2.209 aborts in eval_init / __fortify_fail with gcc-4.4.0-9, but without _FORTIFY_SOURCE it works ok (the same compiler options otherwise).
Comment 6 Jakub Jelinek 2009-06-19 09:24:42 EDT
Please provide preprocessed testcase then and where exactly does it crash (or self-contained reproducer if possible).  And, file it as a separate bug, because this one is fixed.

Note You need to log in before you can comment on or make changes to this bug.