After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 109794 - Crash on large resize
Crash on large resize
Status: RESOLVED DUPLICATE of bug 107234
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Havoc Pennington
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-04-02 15:59 UTC by Sejal Patel
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sejal Patel 2003-04-02 15:55:51 UTC
Package: gnome-terminal
Severity: normal
Version: 2.2.1-1
Synopsis: Crash on large resize
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general

Description:
Description of Problem:
Gnome terminal crashes if you resize the terminal AFTER connecting to
another machine through ssh to a size that spans 2 desktops. It does not
break if you resize the terminal to be that large and then connect
through ssh however. This is done under Metacity window manager if that
helps any on a debian sid system.

Steps to reproduce the problem:
1. Open a terminal. Then connect to another machine through ssh.
2. Then resize the terminal to span the entire desktop horizontally.
3. Click on the title bar and drag most of it off the screen to the
left. Repeat step 2. During the repeat the terminal will crash.

Actual Results:
Terminal crashes.

Expected Results:
Should have a very long terminal.

How often does this happen?
100% if you ssh and then resize. 0% if you resize and then ssh.

Additional Information:
Debian Sid nothing custom installed all debian stuff kernel and all.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-04-02 10:55 -------

Reassigning to the default owner of the component, hp@redhat.com.

Comment 1 Alex Duggan 2003-04-02 20:01:13 UTC
Thanks for the bug report. Without a stack trace from the crash it's
very hard to determine what caused the crash. Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information
about getting a useful stack trace.
Comment 2 Sejal Patel 2003-04-02 20:09:24 UTC
This is easier said then done because I can't simply run the program
inside of gdb because the second a terminal crashes all terminals
crash completely even if they were opened by a completely seperate
user account. Also it does not leave a core file (and yes I did
remember to set the ulimit -c to unlimited). Is there a way to log gdb
results to a file or something.
Comment 3 Sejal Patel 2003-04-07 17:58:06 UTC
Backtrace was generated from '/usr/bin/gnome-terminal'

(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)...(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)...
(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)...(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)...[New
Thread 16384 (LWP 11028)]

(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)...(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)...
(no debugging symbols found)...(no debugging symbols found)...
0x40b64b89 in wait4 () from /lib/libc.so.6

Thread 1 (Thread 16384 (LWP 11028))

  • #0 wait4
    from /lib/libc.so.6
  • #1 sys_sigabbrev
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 __pthread_sighandler
    from /lib/libpthread.so.0
  • #5 sigaction
    from /lib/libc.so.6
  • #6 raise
    from /lib/libpthread.so.0
  • #7 abort
    from /lib/libc.so.6
  • #8 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #9 g_log
    from /usr/lib/libglib-2.0.so.0
  • #10 vte_terminal_fork_command
    from /usr/lib/libvte.so.4
  • #11 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #12 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #16 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 main
  • #18 __libc_start_main
    from /lib/libc.so.6
  • #0 wait4
    from /lib/libc.so.6

Comment 4 John Fleck 2003-04-28 13:11:00 UTC

*** This bug has been marked as a duplicate of 107234 ***