Closed Bug 588738 Opened 14 years ago Closed 14 years ago

warning: perm may be used uninitialized in FilteringWrapper<...>::enumerateOwn

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 578872

People

(Reporter: timeless, Unassigned)

References

Details

js/src/xpconnect/wrappers/FilteringWrapper.cpp:
 In member function ‘bool xpc::FilteringWrapper<...>::enumerateOwn(JSContext*, JSObject*, js::AutoIdVector&) ...:
74: warning: ‘perm’ may be used uninitialized in this function
74: note: ‘perm’ was declared here


67 template <typename Policy>
68 static bool
69 Filter(JSContext *cx, JSObject *wrapper, AutoIdVector &props)
70 {
71     size_t w = 0;
72     for (size_t n = 0; n < props.length(); ++n) {
73         jsid id = props[n];
74         Permission perm;

perm is checked and then assigned to here:
75         if (perm != PermitObjectAccess && !Policy::check(cx, wrapper, id, false, perm))
76             return false; // Error
77         if (perm != DenyAccess) {
78             props[w++] = id;
79         }
80     }
81     props.resize(w);
82     return true;
83 }
Dupe of bug 578872, no?
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
OS: Mac OS X → Windows 7
ooh, it isn't Safari sucks, it's Webkit sucks (that's the level which keeps messing with the platform field)
OS: Windows 7 → Mac OS X
You need to log in before you can comment on or make changes to this bug.