trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2012

Re: [trinity-devel] tdelibs errors

From: "Timothy Pearson" <kb9vqf@...>
Date: Sun, 26 Feb 2012 13:22:02 -0600
> I have working packages. But... they failed rpmlint checking: tdelibs
> failed the build process with the errors at the bottom.
> Can anyone help?
>
> I: A function overflows or underflows an array access. This could be a
> real error,
>    but occasionaly this condition is also misdetected due to loop
> unrolling or strange pointer
>    handling. So this is warning only, please review.
> W: tdelibs arraysubscript
> /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/libkmid/track.cc:337
>
> I: Program is likely to break with new gcc. Try -fno-strict-aliasing.
> W: tdelibs strict-aliasing-punning
> /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/kimgio/dds.cpp:493, 503
> W: tdelibs strict-aliasing-punning
> /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/kioslave/iso/kiso.cpp:252,
> 307, 308, 314
> W: tdelibs strict-aliasing-punning
> /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/libkmid/deviceman.cc:547,
> 560, 579, 601, 622
> W: tdelibs strict-aliasing-punning
> /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/libkmid/fmout.cc:121, 235,
> 237, 238, 243, 280, 290, 302, 316
> W: tdelibs strict-aliasing-punning
> /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/libkmid/gusout.cc:200, 234,
> 236, 237, 241, 276, 298, 312, 407
> W: tdelibs strict-aliasing-punning
> /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/libkmid/midiout.cc:81
> W: tdelibs strict-aliasing-punning
> /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/libkmid/synthout.cc:167,
> 173, 180, 191
> W: tdelibs strict-aliasing-punning
> /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/tdecore/kcrash.cpp:304
>
> I: Program returns random data in a function
> E: tdelibs no-return-in-nonvoid-function
> /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/krsync/rsyncconfigdialog.cpp:180
> E: tdelibs no-return-in-nonvoid-function
> /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/tdecore/kapplication.cpp:198

Put this output into a bug report and raise it to BLOCKER for R14, as some
of these "warnings" could cause crashes during runtime.

Tim