Bug#909328: More information and new backtrace

[Egmont Koblinger]

Hi Léon,

It indeed looks like a gnome-terminal crash. If only vim crashed, you'd
still have both of your terminal windows open.

All your backtraces are about vim. Do you have a backtrace of
gnome-terminal-server? That could help a lot. Without a backtrace, and
without being able to reproduce, unfortunately it's pretty unlikely that
I'll be able to find the problem.

I'm honestly lost about the various contradicting vim backtraces. The one
with SIGHUP, as you say, corresponds to the terminal disappearing, that's
the expected behavior in vim if the terminal crashes. But at the other two
occasions did vim really also segfault? (Now, it could be that vim doesn't
always handle correctly the terminal disappearing, and instead of a clean
SIGHUP exit it segfaults... who know.)

It's a bit suspicious to me that two pieces of software segfault at the
same time. Could it be a faulty hardware? Have you experienced any unusual
behavior in other software? Is there anything suspicious in "dmesg" output?

Could you please do the following for me: in gnome-terminal start "script
-f" and inside that start "vim". Do the ":set lines=999". Does it crash? If
it does, restart gnome-terminal and execute "cat typescript". Does it crash
again? If so, could you please attach this typescript file?

Thanks a lot,
egmont
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20180924/d9e04b6c/attachment.html>