Bug 141152 - pilot-link-0.12.0_pre4-6: 2 * local variable set before used
Summary: pilot-link-0.12.0_pre4-6: 2 * local variable set before used
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: unspecified
Hardware: All SUSE Other
: P5 - None : Minor
Target Milestone: ---
Assignee: Petr Ostadal
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-31 12:02 UTC by David Binderman
Modified: 2006-11-07 16:04 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Binderman 2005-12-31 12:02:41 UTC 
I just tried to compile package pilot-link-0.12.0_pre4-6 with the Intel
C compiler

It said

dlp.c(2279): warning #592: variable "res" is used before its value is set

The source code is

                        LOG((PI_DBG_DLP, PI_DBG_LVL_INFO,
                            "DLP ReadFeature FtrGet error 0x%8.8lX\n",
                            res));

Suggest initialise local variable "res" before first use.

I also tried out the GNU C compiler. It said

read-screenshot.c:105: warning: "f" is used uninitialized in this function

Suggest initialise local variable "f" before first use.


I also had a look at the project website [ http://bugs.pilot-link.org ].
Their current version is 1.8, so I guess they are not interested in bug
reports for 0.12.0.

Is it time to upgrade pilot-link to a newer version ?
Comment 1 Petr Ostadal 2006-01-09 12:27:37 UTC 
Hi David, where did you find the version 1.8 of pilot link?? The current version is 0.12.0_pre4.
Comment 2 Petr Ostadal 2006-01-09 14:09:58 UTC 
fixed uninitialized variable
Comment 3 David Binderman 2006-11-06 10:02:53 UTC 
(In reply to comment #2)
> fixed uninitialized variable

Strange. I just checked Suse Linux 10.2 Beta 1
and both parts of this bug report still appear to
exist.
Comment 4 Petr Ostadal 2006-11-07 16:04:30 UTC 
fixed and submited to stable