Bug 24927 - Avoid empty ResourceError objects in CURL / wx ports
: Avoid empty ResourceError objects in CURL / wx ports
Status: RESOLVED FIXED
Product: WebKit
Classification: Unclassified
Component: WebKit Misc.
: 528+ (Nightly build)
: All All
: P2 Normal
Assigned To: Nobody
: Curl, Wx
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-29 16:43 PDT by Kevin Ollivier
Modified: 2009-05-09 15:42 PDT (History)
2 users (show)

See Also:


Attachments
CURL fix for empty ResourceError object problem (1.33 KB, patch)
2009-03-29 16:44 PDT, Kevin Ollivier
mjs: review+
Details | Formatted Diff | Diff
wx fixes for empty ResourceError objects (5.68 KB, patch)
2009-03-29 16:44 PDT, Kevin Ollivier
mjs: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Ollivier 2009-03-29 16:43:41 PDT
WebCore::DocumentLoader::mainReceivedError now asserts if error.isNull(), and other places may start asserting too, so we need to fill out the ResourceError objects.
Comment 1 Kevin Ollivier 2009-03-29 16:44:20 PDT
Created attachment 29049 [details]
CURL fix for empty ResourceError object problem
Comment 2 Kevin Ollivier 2009-03-29 16:44:54 PDT
Created attachment 29050 [details]
wx fixes for empty ResourceError objects
Comment 3 Maciej Stachowiak 2009-05-09 14:58:20 PDT
Comment on attachment 29049 [details]
CURL fix for empty ResourceError object problem

r=me
Comment 4 Maciej Stachowiak 2009-05-09 14:58:41 PDT
Comment on attachment 29050 [details]
wx fixes for empty ResourceError objects

r=me
Comment 5 Kevin Ollivier 2009-05-09 15:42:03 PDT
Landed in r43442, thanks!