-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
FvwmScript implementation of "For" loop triggers abort on systems with stack protection #299
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
Here is the minimal example script. Remove ".txt" (upload problems). I have run it with FvwmCommand (or MFL client) on FreeBSD and F33 where it crashes, and on OpenBSD and Debian where it is ok. |
FreeBSD with debugging symbols from core dump. If you want FvwmScript binary and core dump binary, I can attach that too.
|
Here they are. |
Hi, I can't reproduce this on FreeBSD-12. Rather -- I can reproduce it if I use I can only conclude that however the |
Yes, but it is the same on Fedora 33, and workaround with While instead of For inside script workarounds this. It is not in environment, I tried in pure FVWM outside NsCDE. However, past year every now and then some people complained me about that for WSM applet, but they were never capable or wilful to go to details and debug. Now that I have various test environments in VMs, I see the same thing. It is happening on NetBSD too, but in some 1/3 cases during start. There must be something in implementation where For and While differs and which causes that. I'll have to look there. Here is richer trace:
|
This can be triggered clearly on the following systems:
This happens with WSM (WSM-4) applet of NsCDE during startup. Here is the trace from Fedora 33, where FvwmScript gets killed by /usr/libexec/gdm-x-session:
FvwmScript code affecting this is here:
https://github.com/NsCDE/NsCDE/blob/master/NsCDE/lib/scripts/WSM-4#L384
If I rewrite this as:
Then it works ok on both F33 and FreeBSD 12-2-RELEASE.
The text was updated successfully, but these errors were encountered: