[opensuse-buildservice] another one I dont understand....
...checking a second package, I get ... running 01-check-debuginfo ... testing for empty debuginfo packages ... running 02-check-gcc-output ... testing for serious compiler warnings (using /usr/lib/build/checks-data/check_gcc_output) (using //.build.log) I: Program returns random data in a function E: hylafax no-return-in-nonvoid-function Trigger.c++:473 System halted. What does that tell me? Whats wrong? Ta! Ax -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, Axel Braun schrieb:
...checking a second package, I get
... running 01-check-debuginfo ... testing for empty debuginfo packages ... running 02-check-gcc-output ... testing for serious compiler warnings (using /usr/lib/build/checks-data/check_gcc_output) (using //.build.log)
I: Program returns random data in a function E: hylafax no-return-in-nonvoid-function Trigger.c++:473 System halted.
What does that tell me? Whats wrong?
That means that there is a non-void function which doesn't return a value in file Trigger.c++ line 473. And as a non-void function should really return a _defined_ value that's wrong in almost all cases. Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hallo Wolfgang, Am Samstag 31 Januar 2009 schrieb Wolfgang Rosenauer:
I: Program returns random data in a function E: hylafax no-return-in-nonvoid-function Trigger.c++:473 System halted.
What does that tell me? Whats wrong?
That means that there is a non-void function which doesn't return a value in file Trigger.c++ line 473. And as a non-void function should really return a _defined_ value that's wrong in almost all cases.
..a problem in the build service? Ax -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Axel Braun escribió:
..a problem in the build service?
No, a problem in the source code of the application you are compiling, very likely a real bug. -- "We have art in order not to die of the truth" - Friedrich Nietzsche Cristian Rodríguez R. Software Developer Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
Am Samstag, 31. Januar 2009 23:31:37 schrieb Wolfgang Rosenauer:
Hi,
Axel Braun schrieb:
...checking a second package, I get
... running 01-check-debuginfo ... testing for empty debuginfo packages ... running 02-check-gcc-output ... testing for serious compiler warnings (using /usr/lib/build/checks-data/check_gcc_output) (using //.build.log)
I: Program returns random data in a function E: hylafax no-return-in-nonvoid-function Trigger.c++:473 System halted.
What does that tell me? Whats wrong?
That means that there is a non-void function which doesn't return a value in file Trigger.c++ line 473. And as a non-void function should really return a _defined_ value that's wrong in almost all cases.
Right, we added this check because the compiler changed its behaviour at some point of time due to optimizations. Old gcc compilers always return a defined value (dunno which one anymore). With current compilers a random value gets returned. So it is really unpredictable what happens now in the application code. Since this might even cause security issues it is really recommended to fix the code (which was also broken before the gcc change) and not to workaround this. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (4)
-
Adrian Schröter -
Axel Braun -
Cristian Rodríguez -
Wolfgang Rosenauer