Closed Bug 422966 Opened 16 years ago Closed 16 years ago

Firefox debugger did not catch critical error

Categories

(Toolkit :: Crash Reporting, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 422308

People

(Reporter: odoketa, Unassigned)

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/523.15 (KHTML, like Gecko) Version/3.0 Safari/523.15
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4

Firefox died with the following error. Error reporting tool that should catch this error did not trap error. Windows then killed process.

Unhandled exception at 0x6010916a in firefox.exe: 0xC0000005: Access violation reading location 0x59595ff0.

6010915E  int         3    
6010915F  int         3    
60109160  mov         ecx,dword ptr [esp+4] 
60109164  or          ecx,0FFFh 
6010916A  mov         eax,dword ptr [ecx-0Fh] 
6010916D  sub         ecx,0Fh 
60109170  test        eax,eax 

Looks like that mov went somewhere bad.

Reproducible: Didn't try

Steps to Reproduce:
1. Unknown - crashed on focus. App responded slowly, then died.
not enough information, it's known that flash is causing breakpad to nor work and that is a flash bug.
Component: OS Integration → Breakpad Integration
Product: Firefox → Toolkit
QA Contact: os.integration → breakpad.integration
Duping unless proven otherwise.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Attachment #309458 - Attachment mime type: text/plain → text/xml;charset=utf-16
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: