-
Notifications
You must be signed in to change notification settings - Fork 107
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
Segmentation faults #123
Comments
To produce a more useful bug report, please includes versions. Which version of Debian are you using? Which version of dvtm are you using? Which terminal (including version) and which shell are you using when the crash occurs? Have you tried it with different terminals (e.g. xterm, konsole) or different shells (e.g. fish, bash, zsh)? Trying different terminals and shells would be useful, I think, assuming you have the time, inclination, and knowledge to do so. Note that I am not a dvtm developer, just a busybody trying to contribute, so feel free to ignore me. :> |
I am experiencing seemingly random, non reproducible segfaults. I am using dvtm-0.15 from Void Linux packages, running on Linux 5.11.22_1 x86_64 using in st 0.8.4 and bash 5.1.8 from Void binary packages. The same setup, apart the continuous package updates has been working without issues for at least 18 months. The issue is non reproducible at will, but it happens when I hit enter for running a command, it happened twice with In dmesg I see:
Any info on what further detail I can provide is appreciated. |
I have exactly the same issue. i'm using
abduco/dvtm crashes from time to time (more than once within one workday)
|
Then this clears out the libxft issue. I think I have noticed this happening when using copy mode (history) in dvtm and the issue seems to be the underlying editor (I use vis for copy mode as well). When my session collapses I remember being able to still see the stuck process, as soon as I kill the copy mode process (a vis instance child of dvtm) the session exits. This happens quite seldom to me though, and I am going by memory. I'll enable trace dump collection and try to save the next one. Any other useful info I should collect? |
i start my abduco session with
and my session terminates with
but the log file contains the info msg about the segfault in dvtm |
It looks like the segfaults are not related to abduco.
the logs gave me
any advice how to get more debug infos? |
On Debian when I run dvtm it just segfaults...
The text was updated successfully, but these errors were encountered: