Closed
Bug 1272432
Opened 8 years ago
Closed 8 years ago
[FlyWeb] Always set attributes in nsDNSServicediscovery when resolving service.
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: djvj, Unassigned)
References
Details
Attachments
(1 file)
1.14 KB,
patch
|
justindarc
:
review+
|
Details | Diff | Splinter Review |
nsDNSServiceDiscovery doesn't set nsDNSServiceInfo::attributes if there are no TXT records in the metadata. It should set the attribute to the empty hash if that's the case, instead of leaving it nullptr. Leaving it null breaks semantics: the nsDNSServiceInfo is supposed to be fully resolved and have all fields defined by the time it gets set to the onServiceResolved callback.
Attachment #8751834 -
Flags: review?(jdarcangelo)
Comment 1•8 years ago
|
||
Comment on attachment 8751834 [details] [diff] [review] always-set-nsdnsserviceinfo-attributes-on-osx.patch Review of attachment 8751834 [details] [diff] [review]: ----------------------------------------------------------------- LGTM
Attachment #8751834 -
Flags: review?(jdarcangelo) → review+
Reporter | ||
Comment 2•8 years ago
|
||
https://hg.mozilla.org/projects/larch/rev/2362715386da
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment on attachment 8751834 [details] [diff] [review] always-set-nsdnsserviceinfo-attributes-on-osx.patch Review of attachment 8751834 [details] [diff] [review]: ----------------------------------------------------------------- ::: netwerk/dns/mdns/libmdns/MDNSResponderOperator.cpp @@ +631,5 @@ > // Resolve TXT record > int count = TXTRecordGetCount(aTxtLen, aTxtRecord); > LOG_I("resolve: txt count = %d, len = %d", count, aTxtLen); > + nsCOMPtr<nsIWritablePropertyBag2> attributes = new nsHashPropertyBag(); > + if (NS_WARN_IF(!attributes)) { return; } This nullcheck is a no-op these days. Our default |operator new| will exit() if the allocation fails, so we'll never get to the if-statement with a null |attributes|.
You need to log in
before you can comment on or make changes to this bug.
Description
•