Closed Bug 198774 Opened 21 years ago Closed 19 years ago

Possibly uninitialized variable detected

Categories

(Core :: XPCOM, defect)

Other
Other
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: m4341, Assigned: dougt)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 Version 1.3, attempted build under HP-UX with HP compilers/linkers

Building under HP-UX 11.00/32-bit results in the following warning, best
displayed with fixed-width font:

Warning 156: "nsRegistry.cpp", line 1273 # The variable 'info' may not be initia
lized on all possible paths from start of the function.
            REGINFO info = { sizeof info, 0, 0 };
                                    ^^^^
Warning 156: "nsRegistry.cpp", line 1299 # The variable 'info' may not be initia
lized on all possible paths from start of the function.
            REGINFO info = { sizeof info, 0, 0 };
                                    ^^^^
Warning 156: "nsRegistry.cpp", line 1741 # The variable 'info' may not be initia
lized on all possible paths from start of the function.
        REGINFO info = { sizeof info, 0, 0 };
                                ^^^^


Reproducible: Always

Steps to Reproduce:
1.
2.
3.
-> xpcom
Assignee: seawood → dougt
Component: Build Config → XPCOM
QA Contact: granrose → scc
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.