-
-
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
Core dump accessing some $[monitor] variables #101
Comments
Hi @afhp-2020, Yeah, not surprised. Please can you get me a |
I have no idea how to do that. Last time I used a debugger on compiled code must have been in the Turbo Pascal timeframe :) I'll be glad to follow any instructions you could provide. |
@afhp-2020,Sure. If you can recompile
... then reproduce your problem, you'll find the coredump in the same place you did before. Then install
... then you'll find a prompt like this:
... in there, type:
... and send me the output here. Thanks! |
Thank you. This and a quick lookup of SO (about redirecting output) helped. Here it is, running For some reason, the debug version would not start my MainPanel but it doesn't really matter. |
Rather than using sscanf() to try and split a string up to a known delimiter (period) which is not valid whitespace, instead use strsep() to tokenise the string and match on the constituent parts. This should avoid segfaults across platforms. Fixes #101
Hi @afhp-2020, Thanks. Please can you have a look at #102 ( Kindly, |
Fixed. All geometry-related monitor variables respond normally, including incomplete references, e.g. What exactly is the meaning of Thanks again for such a prompt fix. |
I'll take a look at the man page, although patches welcome! ;) |
Rather than using sscanf() to try and split a string up to a known delimiter (period) which is not valid whitespace, instead use strsep() to tokenise the string and match on the constituent parts. This should avoid segfaults across platforms. Fixes #101
Rather than using sscanf() to try and split a string up to a known delimiter (period) which is not valid whitespace, instead use strsep() to tokenise the string and match on the constituent parts. This should avoid segfaults across platforms. Fixes fvwmorg#101
Just exploring and checking out the manpage, accessing some of the monitor-related variables will crash fvwm3 and dump core, e.g. Echo $[monitor.whatever] at the FvwmConsole.
The following work:
$[monitor.primary]
,$[monitor.current]
,$[monitor.count]
On the other hand,
$[monitor.output]
and all monitor-specific geometry-related variables crash.Compiled from today's master (76b8e2e) on FreeBSD 12.1-RELEASE-p5 amd64.
Latest core dump, accessing
$[monitor.$[monitor.current].x]
available if that helps (also crashes if monitor name is specified explicitly).The text was updated successfully, but these errors were encountered: