Bug 129677 - 3 * array subscript out of range
Summary: 3 * array subscript out of range
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: X11 Applications (show other bugs)
Version: Final
Hardware: All SuSE Linux 10.0
: P5 - None : Minor
Target Milestone: ---
Assignee: Hendrik Vogelsang
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-20 11:02 UTC by David Binderman
Modified: 2005-10-20 16:10 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Binderman 2005-10-20 11:02:18 UTC
Hello there,

I just tried to compile package bbtools-2005.1.24-4 with a non standard
version of the GNU C compiler. It said

1.

wminterface.cc:71: warning: array subscript out of range

The source code is

        e.xclient.data.l[4] = e.xclient.data.l[5] = 0;

but in the X11 header files, the array l has only five elements, 

        union {
                char b[20];
                short s[10];
                long l[5];
                } data;
} XClientMessageEvent;

so e.xclient.data.l[5] does not exist. Suggest code rework.

2.

wminterface.cc:74: warning: array subscript out of range
wminterface.cc:87: warning: array subscript out of range

Duplicates.
Comment 1 Hendrik Vogelsang 2005-10-20 11:13:32 UTC
please report that to the bbkeys developers not here.

http://bbkeys.sourceforge.net/

btw: bbkeys is under heavy development to match the rework in blackbox 0.7
Comment 2 David Binderman 2005-10-20 16:10:13 UTC
(In reply to comment #1)
> please report that to the bbkeys developers not here.

Thanks for the reply, but I already have done. Twice.

Hence you got it when I couldn't get any reply from developers
mentioned in the package.
 
> btw: bbkeys is under heavy development to match the rework in blackbox 0.7

I had a quick look and it seems that they have three bug 
reports outstanding for five months. 

It looks like this bug report goes to /dev/null. Oh well.
Thanks for responding anyway.