Closed Bug 1832 Opened 26 years ago Closed

purify reports ABR in parser

Categories

(Core :: DOM: HTML Parser, defect, P1)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: buster, Assigned: rickg)

Details

I loaded each sample, and starwave.com. Don't know which page triggered this. ============== report ================ [E] ABR: Array bounds read in CNavDTD::HandleDefaultStartToken(CToken *,nsHTMLTag,nsIParserNode&) {18 occurrences} Reading 4 bytes from 0x0455346c (4 bytes at 0x0455346c illegal) Address 0x0455346c is 4 bytes before the beginning of a 120 byte block at 0x04553470 Address 0x0455346c points to a C++ new block in heap 0x04320000 Thread ID: 0xae Error location CNavDTD::HandleDefaultStartToken(CToken *,nsHTMLTag,nsIParserNode&) [CNavDTD.cpp:842] CNavDTD::HandleStartToken(CToken *) [CNavDTD.cpp:932] NavDispatchTokenHandler(CToken *,nsIDTD *) [CNavDTD.cpp:446] CTokenHandler::()(CToken *,nsIDTD *) [nsTokenHandler.cpp:80] CNavDTD::HandleToken(CToken *,nsIParser *) [CNavDTD.cpp:697] nsParser::BuildModel(void) [nsParser.cpp:724] nsParser::ResumeParse(void) [nsParser.cpp:688] nsParser::OnDataAvailable(nsIURL *,nsIInputStream *,int) [nsParser.cpp:929] nsDocumentBindInfo::OnDataAvailable(nsIURL *,nsIInputStream *,int) [nsDocLoader.cpp:1553] OnDataAvailableProxyEvent::HandleEvent(void) [nsNetThread.cpp:606] Allocation location new(UINT) [new.cpp:23] nsTagStack::nsTagStack(int) [nsDTDUtils.cpp:39] nsDTDContext::nsDTDContext(int) [nsDTDUtils.cpp:144] CNavDTD::CNavDTD(void) [CNavDTD.cpp:516] NS_NewNavHTMLDTD(nsIDTD * *) [CNavDTD.cpp:412] CNavDTD::CreateNewInstance(nsIDTD * *) [CNavDTD.cpp:544] FindSuitableDTD(CParserContext&,nsString&) [nsParser.cpp:394] nsParser::WillBuildModel(nsString&,nsIDTD *) [nsParser.cpp:497] nsParser::OnDataAvailable(nsIURL *,nsIInputStream *,int) [nsParser.cpp:923] nsDocumentBindInfo::OnDataAvailable(nsIURL *,nsIInputStream *,int) [nsDocLoader.cpp:1553]
Priority: P2 → P1
Status: NEW → ASSIGNED
All fixed with latest update to parser. You'll see the checkin on MOnday or so.
steve can you verify the fix?
rickg should verify this. Note that he is on vacation this week.
rick can you please verify, we do not have the ability to do so at this time.
I should also have said -- "or provide a test case for verification"
QA Contact: 4141
Status: RESOLVED → VERIFIED
no new update from engineer.
You need to log in before you can comment on or make changes to this bug.