Summary: | ASSERT(m_state = Open); is bad news bears | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Adam Barth <abarth> | ||||
Component: | New Bugs | Assignee: | Adam Barth <abarth> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ap, darin | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Other | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
Adam Barth
2010-10-03 02:15:31 PDT
Created attachment 69586 [details]
Patch
Comment on attachment 69586 [details]
Patch
With gcc 4.5 would write a plugin to inspect basic blocks for ASSERTs... Good catch!!!!
Committed r68986: <http://trac.webkit.org/changeset/68986> Good to fix, but nearly harmless; the effect is local to the assertion. In a debug build we simply lose the assertion; but if the assertion was true then the statement has no effect. In a release build the expression is not even compiled. Sure, but the bad case is if the assertion is false. Then the statement masks the problem in Debug builds, but Release builds behave differently. Good catch! |