GNOME Bugzilla – Bug 135799
Funny escape characters seemed to kill off gnome-terminal
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 1 (Yarrow) Package: gnome-terminal Severity: major Version: GNOME2.4.0 unspecified Gnome-Distributor: GNOME.Org Synopsis: Funny escape characters seemed to kill off gnome-terminal Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: I use qpsmtpd on my mail server, server.lerner.co.il. I was running "tail -f" on the logging output from my qpsmtpd installation. I heard a "beep," switched back to that terminal to see what was happening, and discovered that I had gotten into VT1xx escape mode, where lowercase characters can be used for drawing lines. Moments after I saw this, gnome-terminal crashed on me. I was also running "tail -f" on the output from another (local) program, and two other tabs, for a total of four terminal sessions. But I've used four tabs in the past without any trouble, so I doubt that's the problem. Steps to reproduce the crash: 1. Run "tail -f" on qpsmtpd output 2. Wait for someone to send you mail that switches into VT1xx escape mode 3. Boom! Expected Results: I expect that gnome-terminal will show the characters, weird as they are. How often does this happen? This the first time gnome-terminal has ever crashed on me. Additional Information: I'm running Fedora Core 1, kept up-to-date with apt-rpm. Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1085250912 (LWP 3915)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x0027fc32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 44677
Thread 1 (Thread -1085250912 (LWP 3915))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-02-29 19:51 ------- Reassigning to the default owner of the component, gnome-terminal-maint@bugzilla.gnome.org.
This has been fixed a while ago. Note that running tail -f on logs which contain unchecked data is very insecure. Terminals should of course not segfault, but you do not really want to send stuff to terminals which you don't know about. You can use less -F, iirc, because less escapes control characters... *** This bug has been marked as a duplicate of 107262 ***