-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
src: fix intermittent SIGSEGV in resolveTxt #960
Conversation
Are we upstreaming these or are we giving up on working with c-ares? |
Oh, sorry, this is the wrap. Ignore that comment then! LGTM and we can get this in 1.4.0. |
The following code reproduces the error with a well known site. Do you think it's worth adding this to the internet test suite? var dns = require('dns');
dns.resolveTxt('www.microsoft.com', function(err, res) {
console.log(err);
console.log(res);
}); |
@cjihrig probably .. it's simple enough and should probably go in test/internet |
k, ill add that |
Fixes a SIGSEGV by making sure `txt_chunk` is not empty before setting it on `txt_records`
4b18550
to
b59c1f2
Compare
Test has been added |
lgtm, land it |
Fixes a SIGSEGV by making sure `txt_chunk` is not empty before setting it on `txt_records` PR-URL: #960 Reviewed-By: Rod Vagg <rod@vagg.org>
Landed in e435a01 |
Fixes a SIGSEGV by making sure `txt_chunk` is not empty before setting it on `txt_records` PR-URL: nodejs/node#960 Reviewed-By: Rod Vagg <rod@vagg.org>
Fixes a SIGSEGV by making sure
txt_chunk
is not empty before settingit on
txt_records
Ref: nodejs/node-v0.x-archive#9285