-
Notifications
You must be signed in to change notification settings - Fork 30k
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
OpenBSD: Crash on dns.resolve() #52439
Labels
dns
Issues and PRs related to the dns subsystem.
Comments
Will other DNS queries cause the crash ? |
Yes, the name doesn't matter and neither does the rrtype - both 'A' and 'AAAA' queries lead to the same crash |
|
Nope, that works:
|
The same issue occurs on 20.12.2 |
Tracked it down to an OpenBSD specific bug in c-ares. |
VlkrS
added a commit
to VlkrS/c-ares
that referenced
this issue
May 8, 2024
As described in c-ares#753 the change merged with c-ares#659 is ill-advised and leads to breakage in applications using c-ares on OpenBSD. See also nodejs/node#52439
4 tasks
nodejs-github-bot
pushed a commit
that referenced
this issue
Nov 1, 2024
PR-URL: #55521 Fixes: #52439 Reviewed-By: Luigi Pinca <[email protected]>
RafaelGSS
pushed a commit
that referenced
this issue
Nov 1, 2024
PR-URL: #55521 Fixes: #52439 Reviewed-By: Luigi Pinca <[email protected]>
louwers
pushed a commit
to louwers/node
that referenced
this issue
Nov 2, 2024
PR-URL: nodejs#55521 Fixes: nodejs#52439 Reviewed-By: Luigi Pinca <[email protected]>
tpoisseau
pushed a commit
to tpoisseau/node
that referenced
this issue
Nov 21, 2024
PR-URL: nodejs#55521 Fixes: nodejs#52439 Reviewed-By: Luigi Pinca <[email protected]>
ruyadorno
pushed a commit
that referenced
this issue
Nov 27, 2024
PR-URL: #55521 Fixes: #52439 Reviewed-By: Luigi Pinca <[email protected]>
ruyadorno
pushed a commit
that referenced
this issue
Nov 27, 2024
PR-URL: #55521 Fixes: #52439 Reviewed-By: Luigi Pinca <[email protected]>
ruyadorno
pushed a commit
that referenced
this issue
Nov 27, 2024
PR-URL: #55521 Fixes: #52439 Reviewed-By: Luigi Pinca <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
18.19.1
Platform
OpenBSD 7.5-current
Subsystem
src/cares-wrap.cc
What steps will reproduce the bug?
On OpenBSD 7.5-current,
with node 18.19.1, built with --shared-libuv, --shared-cares
and libuv 1.48.0, libcares 1.28.0
(same for node 18.20.1)
How often does it reproduce? Is there a required condition?
Occurs on every attempt
What is the expected behavior? Why is that the expected behavior?
No crash :-)
What do you see instead?
A crash due to a failed assertion, see above.
Additional information
I realize that node v18.x chose to revert libuv to 1.44.2 and that the project cannot support non-tested setups such as this one, but since I confirmed that on FreeBSD with the same versions of node, libuv and libcares the problem does not occur, I was hoping that you might be able to suggest under which conditions the assertion in cares-wrap.cc:685 might fail.
The text was updated successfully, but these errors were encountered: