GNOME Bugzilla – Bug 160759
crashes when resizing window with minicom running
Last modified: 2005-03-02 22:43:46 UTC
Distribution: Red Hat Linux release 9 (Shrike) Package: gnome-terminal Severity: normal Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: crashes when resizing window with minicom running Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Steps to reproduce the crash: 1. open window 2. open minicom 3. resize window Expected Results: How often does this happen? every time one does it Additional Information: 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 -1208099968 (LWP 3112)] [New Thread 113810352 (LWP 3128)] [Thread debugging using libthread_db enabled] [New Thread -1208099968 (LWP 3112)] [New Thread 113810352 (LWP 3128)] [Thread debugging using libthread_db enabled] [New Thread -1208099968 (LWP 3112)] [New Thread 113810352 (LWP 3128)] (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)...0x00c097a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 53283
Thread 1 (Thread -1208099968 (LWP 3112))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-08 05:03 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-terminal". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Appears to be a unique stack trace, according to the simple-dup-finder. Some questions: It looks like you're running on Red Hat 9, which ships with Gnome 2.2, but the report says you're running Gnome 2.8 which means that you must have compiled it yourself. However, the stack trace shows libraries are pulled from /usr/lib which means that when you compiled you may have not set up things correctly. What version of Gnome, and in particular gnome-terminal, are you running? Did you compile Gnome 2.8 yourself? Where did you install it to?
I'm really running daily rawhide, please disregard the contents of /etc/redhat-release (it's just being used by the packaging system to decide what branch to serve files off)
Ah, ok. That's Gnome 2.9.x, right?
It's 2.8.x still :) % rpm -q gnome-terminal gnome-terminal-2.8.0-2 Sorry for the confusion.
Okay, I'll drop the version back down. Also, due to the stack trace, I should have reassigned this to vte; I'm doing so now.
Created attachment 38148 [details] [review] relax the assertion This patch makes the assertion a bit more relaxed. (Allow pending->len to be 0) Also removes some stale debugging code using a struct member that has been removed . Please test and see if this breaks in any other cases - it fixes the crash for me at least.
I guess this is nothing more than a band aid though. Maybe there's some off by one when setting terminal->pvt->pending->len or something that's causing it to be 0 when it shouldn't be?
There's a patch to fix this in bug #163814. Marking this as duplicate of that. *** This bug has been marked as a duplicate of 163814 ***