Skip to content
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

Causes WeeChat 1.9-2 (Arch) to crash #2

Open
kenb0t opened this issue Aug 4, 2017 · 5 comments
Open

Causes WeeChat 1.9-2 (Arch) to crash #2

kenb0t opened this issue Aug 4, 2017 · 5 comments
Assignees

Comments

@kenb0t
Copy link

kenb0t commented Aug 4, 2017

correction_completion.py from https://weechat.org/files/scripts/correction_completetion.py causes WeeChat 1.9-2 (x86_64), from the community Arch-Linux repo, to crash when the script is loaded due to SIGSEGV.

To reproduce, load the script. If autoload is enabled, crash occurs at launch.

Reverting to WeeChat 1.9-1 resolves the issue, which makes me wonder if this is a bug in the script or the app. I decided on the script somewhat arbitrarily (I have a bunch of scripts from the scripts plugin and this is the only one that causes an issue).

@pSub
Copy link
Owner

pSub commented Aug 19, 2017

Thanks for the report. I'll try to look into it in the next few days.

@pSub
Copy link
Owner

pSub commented Mar 17, 2018

I could reproduce the error on Arch and Ubuntu. However I am unable to reproduce it on NixOS, my main operating system.

@pSub
Copy link
Owner

pSub commented Mar 17, 2018

I suspect it has something to do with Position Independent Executables (PIE). The Arch package broke exactly when migrating to PIEs. The error also seems independent of the weechat version, as my Ubuntu installation ships a very old one and suffers from the same problem and is compiled as a PIE.

@winnieXY
Copy link

Any news here? The correction_completion script is still crashing weechat.

@pSub
Copy link
Owner

pSub commented Feb 22, 2024

Unfortunately, no news here. I haven't looked into this issue for quite some time. I'll look into it in the next days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants