Segfault on connect
See original GitHub issueTried running example from readme on my linux machine and received segfault when connect
method was called.
node 10.4.1 tdl latest tdlib 1.2.0
PID 15192 received SIGSEGV for address: 0x10
node(EVP_MD_CTX_clear_flags+0x6)[0x13734a6]
node(EVP_DigestInit_ex+0x1e)[0x135d3de]
node(HMAC_Init_ex+0x153)[0x137cb93]
/app/deps/td/build/libtdjson.so(+0x881c1b)[0x7f687f6f5c1b]
/app/deps/td/build/libtdjson.so(+0x88cc70)[0x7f687f700c70]
/app/deps/td/build/libtdjson.so(+0x8b37bd)[0x7f687f7277bd]
/app/deps/td/build/libtdjson.so(+0x8cf99f)[0x7f687f74399f]
/app/deps/td/build/libtdjson.so(+0x8dece0)[0x7f687f752ce0]
/app/deps/td/build/libtdjson.so(+0x8dee7f)[0x7f687f752e7f]
/app/deps/td/build/libtdjson.so(+0x8e3c67)[0x7f687f757c67]
/app/deps/td/build/libtdjson.so(+0x918fc1)[0x7f687f78cfc1]
/app/deps/td/build/libtdjson.so(+0x91a407)[0x7f687f78e407]
/app/deps/td/build/libtdjson.so(+0x91b6b2)[0x7f687f78f6b2]
/app/deps/td/build/libtdjson.so(+0x91b956)[0x7f687f78f956]
/app/deps/td/build/libtdjson.so(+0x9104d9)[0x7f687f7844d9]
/app/deps/td/build/libtdjson.so(+0x91a407)[0x7f687f78e407]
/app/deps/td/build/libtdjson.so(+0x90dc6a)[0x7f687f781c6a]
/app/deps/td/build/libtdjson.so(+0x8650bc)[0x7f687f6d90bc]
/app/deps/td/build/libtdjson.so(+0x867660)[0x7f687f6db660]
/app/deps/td/build/libtdjson.so(+0x29bcc0)[0x7f687f10fcc0]
/app/deps/td/build/libtdjson.so(+0x29d30b)[0x7f687f11130b]
/app/deps/td/build/libtdjson.so(+0x29dd31)[0x7f687f111d31]
/app/deps/td/build/libtdjson.so(+0x268bf7)[0x7f687f0dcbf7]
/app/deps/td/build/libtdjson.so(+0x26df3c)[0x7f687f0e1f3c]
/app/deps/td/build/libtdjson.so(+0x168cac)[0x7f687efdccac]
/app/deps/td/build/libtdjson.so(+0x871bef)[0x7f687f6e5bef]
/app/deps/td/build/libtdjson.so(+0x87616a)[0x7f687f6ea16a]
/app/deps/td/build/libtdjson.so(+0x8764d9)[0x7f687f6ea4d9]
/app/deps/td/build/libtdjson.so(+0x876c68)[0x7f687f6eac68]
/app/deps/td/build/libtdjson.so(+0x86ebf2)[0x7f687f6e2bf2]
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
qt signals cause segmentation fault on connect - Stack Overflow
1 Answer 1 · Null pointers should result in connect returning false according to the source. Uninitialized pointers could do just about anything ......
Read more >Thread: Connect call causes a SEGFAULT - Qt Centre Forum
Hey all, The code compiles and links w/o issue. Here's where I make the connect() call in my MainWindow class.
Read more >Segmentation Fault when using SSL to connect inside a ...
I've provided the node-pg client connecting successfully alongside the segfault in the repo below.
Read more >MySQL Workbench Segmentation Fault after Connecting to DB
Program opens successfully, but when connecting to a database, after entering the password the program crashes with a segfault. How to repeat: ...
Read more >Identify what's causing segmentation faults (segfaults) - IU KB
A segmentation fault (aka segfault) is a common condition that causes programs to crash; they are often associated with a file named core...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok. Seems I’ve got the root cause. Node.js that came from nvm should be compiled with the same version of openssl that tdlib. If they have different versions, then it will receive segfault.
Thanks.
I’ve tried latest node that uses openssl 1.1.X and tdlib with openssl 1.0.1 and 1.0.2 - received segfaults.