MacOS: got 139 (interrupted by signal 11: SIGSEGV) about chatgpt HOT 25 CLOSED

@TccccD It's an issue with your Python interpreter. Update to Python 3.10.6 for the most reliability

from chatgpt.

Also update the package pip3 install revChatGPT --upgrade

from chatgpt.

I have python 3.10.8, having the same issue : Segmentation fault: 11
OS : Macos catalina

from chatgpt.

Data streaming might not work with MacOS.

I just updated the code again. pip3 install revChatGPT --upgrade

It is probably an issue with data streams. Streaming is now optional with --stream

Running normally should work now

from chatgpt.

@TccccD @lafroujianas Could you test this?

from chatgpt.

Still getting "Segmentation fault: 11" on macos catalina

from chatgpt.

What python version?

from chatgpt.

I don't use MacOS so I can't really replicate. You can try using gbd to debug

from chatgpt.

Python 3.10.8

from chatgpt.

I have no idea why this is happening. Might need feedback from more MacOS users. I have not used any advanced Python, only basic requests, json, and bs4. Can you show the full output? Does it crash immediately or is there a certain point at which it crashes?

from chatgpt.

from chatgpt.

I think the issue is from : in revChatGPT.py import tls_client

If I remove the line, the code is executed (with error), with with node Segmentation fault

from chatgpt.

I'm on MacOS, and I have Python 3.6 to 3.11, Code works ok. This is not an issue with tls_client, but a misconfiguration in your system which makes tls_client fail.

from chatgpt.

https://stackoverflow.com/questions/49414841/process-finished-with-exit-code-139-interrupted-by-signal-11-sigsegv

from chatgpt.

I think I'm having a similar problem. I'm using revChatGPT inside a docker container in a Raspberry Pi (arm64) and I get the following from the docker logs
Traceback (most recent call last): File "/app/app.py", line 6, in <module> from revChatGPT.revChatGPT import Chatbot File "/usr/local/lib/python3.9/site-packages/revChatGPT/revChatGPT.py", line 8, in <module> import tls_client File "/usr/local/lib/python3.9/site-packages/tls_client/__init__.py", line 15, in <module> from .sessions import Session File "/usr/local/lib/python3.9/site-packages/tls_client/sessions.py", line 1, in <module> from .cffi import request File "/usr/local/lib/python3.9/site-packages/tls_client/cffi.py", line 15, in <module> library = ctypes.cdll.LoadLibrary(f'{root_dir}/dependencies/tls-client{file_ext}') File "/usr/local/lib/python3.9/ctypes/__init__.py", line 452, in LoadLibrary return self._dlltype(name) File "/usr/local/lib/python3.9/ctypes/__init__.py", line 374, in __init__ self._handle = _dlopen(self._name, mode) OSError: /usr/local/lib/python3.9/site-packages/tls_client/dependencies/tls-client-amd64.so: cannot open shared object file: No such file or directory

Somehow I think it's trying to get amd64 instead of arm64. Do you know how to correct this?

from chatgpt.

Arm and 32bit are not supported yet. https://github.com/FlorianREGAZ/Python-Tls-Client/issues

You must use session tokens if you're on one of these platforms

from chatgpt.

@rawandahmad698
Any ideas on alternatives to TLS-Client?

from chatgpt.

I have python 3.10.8, having the same issue : Segmentation fault: 11 OS : Macos catalina

I was experiencing the same issue; updating from Catalina to Big Sur resolved it for me.

from chatgpt.

Upgrading from Mac OS Catalina solved it for me.

from chatgpt.

Upgrading from Mac OS Catalina solved it for me. +1

from chatgpt.

same error on my ubuntu 20; ...

from chatgpt.

@xs-fj You might be using 32bit Python

from chatgpt.

/site-packages/tls_client/dependencies/tls-client-amd64.so: cannot open shared object file: No such file or directory

Same errors; run in 64bit ubuntu 20 ...

from chatgpt.

tls-client uses closed soured libs from anywhere (tls-client-x86.dylib). As we don't know, where this lib comes from and what is does, this is a real security issue. Remember: you provide this source with username and password or even with access tokens. (Maybe the source sends it to somewhere ... ;-)

from chatgpt.

tls-client uses closed soured libs from anywhere (tls-client-x86.dylib). As we don't know, where this lib comes from and what is does, this is a real security issue. Remember: you provide this source with username and password or even with access tokens. (Maybe the source sends it to somewhere ... ;-)

We do know where it comes from. It is ripped directly from https://github.com/bogdanfinn/tls-client/tree/master/cffi_dist/dist

from chatgpt.