Red Hat Bugzilla – Bug 149399
2 * array subscript out of range
Last modified: 2007-11-30 17:11:00 EST
Description of problem:
I just tried to compile package bbkeys-0.8.6-4 from
Redhat Fedora Extras development tree.
The compiler said
wminterface.cc(71): warning #175: subscript out of range
The source code is
e.xclient.data.l = e.xclient.data.l = 0;
but in file /usr/X11R6/include/X11/Xlib.h, field l only has five
longs, so e.xclient.data.l doesn't exist.
Suggest code rework.
wminterface.cc(89): warning #175: subscript out of range
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I saw that you were opening quite a few similar reports for many
components... please, just a few questions :
- What is the consequence exaclty? Just compiler warnings? How does
this affect the behavior?
- Why do you report these coding problems to _packagers_ instead of to
the upstream _developers_?
>What is the consequence exaclty?
Depends. If the rest of the union is bigger (might be on some
machines), then reasonably safe - if not, then other data is overwritten.
In a strict sense, accessing an array outside its limits is
>Why do you report these coding problems to _packagers_
Redhat Fedora asks for bug reports, they get bug reports.
Why ask for bug reports, then complain when I send them in ?
Having a single point of contact for bug reports helps me a lot.
The packagers are free to forward the bug reports on to relevant
I'll be working my way through Extras over the next few days.
First impressions are that I'm going to be finding a lot of bugs.
A rebuild of bbkeys 0.9.0 will appear in Extras development real soon. Please
check if the problem still exists in that new version, as it includes major changes.
>Please check if the problem still exists in that new version
Sorry, unable to do so.
That machine no longer runs any Redhat Linux.
I suspect that a swift visual check of the new version by Mark 1 eyeball
will be able to verify whether or not the bug still exists.
Thanks for the bug report. At the moment, the Fedora developers don't have
time to work on this particular issue. The best way to make sure your problem
will get looked on is to report it to the authors of the program. Most
upstream authors use a bug tracking system like bugzilla, and more people
who know the code will be looking at the bug report there.
The upstream bug tracking system to use is:
Please make sure the bug isn't already in the upstream bug tracker before