Closed
      
        Bug 899402
      
      
        Opened 12 years ago
          Closed 10 years ago
      
        
    
  
runtime error: member call on null pointer of type 'js::ion::IonJSFrameLayout'  
    Categories
(Core :: JavaScript Engine, defect)
        Core
          
        
        
      
        
    
        JavaScript Engine
          
        
        
      
        
    Tracking
()
        RESOLVED
        DUPLICATE
          of bug 1165904
        
    
  
People
(Reporter: yeukhon, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [-fsanitize=null])
Attachments
(1 file)
| 
        
        
         8.99 KB,
          text/plain         
       | 
      Details | 
This is the bug following https://bugzilla.mozilla.org/show_bug.cgi?id=899399.
The full stack trace can be seen from that bug ticket, but I am attaching the subset (the relevant) here.
| Reporter | ||
          Updated•12 years ago
           
         | 
      
Whiteboard: [-fsanitize=null] → [-fsanitize=undefined]
          Updated•12 years ago
           
         | 
      
Whiteboard: [-fsanitize=undefined] → [-fsanitize=null]
          Updated•12 years ago
           
         | 
      
Summary: runtime error: member call on null point er of type 'js::ion::IonJSFrameLayout' → runtime error: member call on null pointer of type 'js::ion::IonJSFrameLayout'
          Comment 1•12 years ago
           
         | 
      ||
../ion/shared/IonFrames-x86-shared.h:72:42: runtime error: member call on null pointer of type 'js::ion::IonJSFrameLayout'
          Comment 2•12 years ago
           
         | 
      ||
This code so obviously wrong I'm surprised none of our compilers optimize the entire function into __builtin_unreachable.
Introduced:    http://hg.mozilla.org/mozilla-central/rev/b02a7b214e49#l12.12
Spread:        http://hg.mozilla.org/mozilla-central/rev/fd94cdea9dad
Keywords: regression
          Comment 3•12 years ago
           
         | 
      ||
(In reply to Jesse Ruderman from comment #2)
> This code so obviously wrong I'm surprised none of our compilers optimize
> the entire function into __builtin_unreachable.
Because this is a well supported undefined behavior.
and so this is not critical at all unless somebody want to change the value of the constant NULL.
| Assignee | ||
          Updated•11 years ago
           
         | 
      
Assignee: general → nobody
          Updated•10 years ago
           
         | 
      
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•