Closed
Bug 172740
Opened 23 years ago
Closed 23 years ago
"use of uninitialized variable" warnings
Categories
(Bugzilla :: Query/Bug List, defect)
Tracking
()
VERIFIED
FIXED
Bugzilla 2.18
People
(Reporter: bbaetz, Assigned: gerv)
Details
Attachments
(1 file)
|
1.06 KB,
patch
|
bbaetz
:
review+
bbaetz
:
review+
|
Details | Diff | Splinter Review |
Try doing a search:
buglist.cgi: Use of uninitialized value in string eq at
/var/www/html/bugzilla-misc/buglist.cgi line 86.
You need to test $::FORM{'format'} before doing the string compare
buglist.cgi: Use of uninitialized value in substitution (s///) at globals.pl
line 1643.
buglist.cgi: Use of uninitialized value in pattern match (m//) at
Bugzilla/Util.pm line 114.
These are because GetFormat has:
$ctype ||= "html";
# Security - allow letters and a hyphen only
$ctype =~ s/[^a-zA-Z\-]//g;
$format =~ s/[^a-zA-Z\-]//g;
trick_taint($ctype);
trick_taint($format);
but doesn't check to see if $format was undef first. You need
$format ||= "";
| Assignee | ||
Comment 1•23 years ago
|
||
Fix problem, plus another one I noticed in my error log.
Gerv
| Reporter | ||
Comment 2•23 years ago
|
||
Comment on attachment 101889 [details] [diff] [review]
Patch v.1
r=bbaetz, but this doesn't include teh 'other issue' you saw in the logs...
Attachment #101889 -
Flags: review+
| Assignee | ||
Comment 3•23 years ago
|
||
Yes, it does :-) The second change is actually unrelated to the first.
Checking in globals.pl;
/cvsroot/mozilla/webtools/bugzilla/globals.pl,v <-- globals.pl
new revision: 1.210; previous revision: 1.209
done
Checking in buglist.cgi;
/cvsroot/mozilla/webtools/bugzilla/buglist.cgi,v <-- buglist.cgi
new revision: 1.198; previous revision: 1.197
done
Gerv
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 4•23 years ago
|
||
Yeah, but thats the first thing I mentioned in comment 0 :)
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Target Milestone: --- → Bugzilla 2.18
Updated•13 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•