-
Notifications
You must be signed in to change notification settings - Fork 0
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
Comments
Thanks for the report. I'll try to look into it in the next few days. |
I could reproduce the error on Arch and Ubuntu. However I am unable to reproduce it on NixOS, my main operating system. |
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. |
Any news here? The correction_completion script is still crashing weechat. |
Unfortunately, no news here. I haven't looked into this issue for quite some time. I'll look into it in the next days. |
poke.. any hope on this one? :) if not, thanks anyways! |
This is strange error. From time to time I investigate, but most of the time without any real progress. I just googled a little bit to see if someone has a similar problem and stumbled upon libhugetlbfs/libhugetlbfs#49 and facebookarchive/BOLT#52. This sounds very similar. I don't have much time right now, but this gives me some hope and I will try to dive deeper into it. |
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).
The text was updated successfully, but these errors were encountered: