Closed Bug 51662 Opened 24 years ago Closed 24 years ago

UMR in normalize_forward

Categories

(Core :: XPCOM, defect, P3)

Product:
Core
Component:
XPCOM
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: jband_mozilla, Assigned: scc)

References

Details

Attachments

(2 files)

sample location info from Purify
1.76 KB, text/plain
Details
here's the patch I'll apply when the tree opens; I was initializing |mPosition| out of order
1.20 KB, patch
Details | Diff | Splinter Review 
Running under Purify I get gazillions of Uninitialized Memory Reads in...

nsReadingIterator<WORD>::normalize_forward(void)
  and
nsWritingIterator<WORD>::normalize_forward(void)

A quick look at the code does not enlighten me on the question of how anything 
here could be uninitialized.

I'm going to have to filter these out (and forget them) in order to do anything 
useful in Purify.

    
  
Status: NEW → ASSIGNED

    
    

    
  
*** Bug 51836 has been marked as a duplicate of this bug. ***

    
    

    
  
Thanks to David Bienvenu, by the way, for tracking down my problem, here.


    
    

    
  
fix checked in


    
    

    
  
no complaints, I'm assuming this fixes it ... marking fixed

Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED

    
    

    
  
verified.
Status: RESOLVED → VERIFIED

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: