Closed
Description
- Version: v14.15.1
- Platform: Linux 5.8.0-38-generic The binary and long term compatibility with node #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
- Subsystem: TLSSocket.prependOnceListener
What steps will reproduce the bug?
Setup a node instance,
» node
and run the following javascript code.
tlsSocket = tls.connect('r','\u{85}');
tlsSocket.prependOnceListener('keylog',(line)=>{});
Then a segmentation fault occurs.
How often does it reproduce? Is there a required condition?
This problem can always be triggered following the steps above.
What is the expected behavior?
If any error occurs, an exception or other similar error-reporting stuff should be thrown. There is no reason to abort the whole node process.
What do you see instead?
» node
Welcome to Node.js v14.15.1.
Type ".help" for more information.
> tlsSocket = tls.connect('r','\u{85}');
<ref *1> TLSSocket {
...
}
> tlsSocket.prependOnceListener('keylog',(line)=>{});Uncaught:
<ref *1> Error: connect ENOENT r
...
}
> tlsSocket.prependOnceListener('keylog',(line)=>{});
[1] 210623 segmentation fault (core dumped) node