[Bug 515041] New: lirc-0.8.5-1.3:array index out of range
http://bugzilla.novell.com/show_bug.cgi?id=515041 Summary: lirc-0.8.5-1.3:array index out of range Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dcb314@hotmail.com QAContact: qa@suse.de Found By: --- I just had a look at factory package lirc-0.8.5-1.3 In file lirc-0.8.5/daemons/hw_commandir.c around line 834, is the source code for(i=0;i<MAX_CHANNELS;i++) { next_signalq_per_channel[i] = -1; channels_en[i] = 0xff; but static char channels_en[MAX_DEVICES]; and lirc-0.8.5/daemons/hw_commandir.h:#define MAX_DEVICES 4 lirc-0.8.5/daemons/hw_commandir.h:#define MAX_CHANNELS 16 This looks like broken code because the array channels_en only has four entries, but 16 are written into it. Suggest code rework. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=515041 Marcus Meissner <meissner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |lnussel@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=515041 User rguenther@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=515041#c1 --- Comment #1 from Richard Guenther <rguenther@novell.com> 2009-10-17 08:54:22 MDT --- David, in case the issues are not introduced by a patch local to openSUSE please report the issues upstream. Packagers, please do not add openSUSE-local patches to fix this kind of errors but forward the bugs upstream and close the bugs as RESOLVED UPSTREAM. Note that it is perfectly fine to have "resource leaks" at the end of a program as the kernel will clean up for you. Manually freeing them only increases binary size and runtime. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=515041 https://bugzilla.novell.com/show_bug.cgi?id=515041#c2 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #2 from Ludwig Nussel <lnussel@suse.com> 2013-07-05 09:49:25 CEST --- Looks like the code was rewritten upstream. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com