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 100201 - gnome-terminal crash. Using two-tabs; ssh & gdb
gnome-terminal crash. Using two-tabs; ssh & gdb
Status: RESOLVED DUPLICATE of bug 94509
Product: gnome-terminal
Classification: Core
Component: general
2.0.x
Other Linux
: Normal critical
: ---
Assigned To: Havoc Pennington
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-12-03 05:56 UTC by Elijah Newren
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description Elijah Newren 2002-12-03 05:56:32 UTC 
I'm guessing that this bug should be filed under vte (due to the "vte*"
functions in the stacktrace), but since I'm not sure I'm filing it
against gnome-terminal.

I don't know what's relevant, so here's what happened and what I did:

1. Immediately upon login, battstat crashes
2. Bug-buddy fires up but doesn't get a backtrace
3. I launch a gnome-terminal
4. I open a second tab and ssh to my school account to read my email (in
order to find out how to get a stack trace using gdb when bug-buddy
doesn't get one)
5. I go back to the original tab and run gdb; attach to the process, and
get a stack trace.
6. The stack trace is long so I extend the vertical size of the
gnome-terminal window a couple times and move it upwards.
7. Gnome-terminal crashes.

How often does this happen?
This is the first time.  I'll see if I can somehow reproduce it later,
unless this is already a duplicate of what others have found.

Backtrace was generated from '/usr/bin/gnome-terminal'

(no debugging symbols found)...[New Thread 8192 (LWP 1689)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 31215

Thread 1 (Thread 8192 (LWP 1689))

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 kill
    from /lib/i686/libc.so.6
  • #7 raise
    from /lib/i686/libpthread.so.0
  • #8 abort
    from /lib/i686/libc.so.6
  • #9 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #10 g_log
    from /usr/lib/libglib-2.0.so.0
  • #11 vte_terminal_ensure_cursor
    from /usr/lib/libvte.so.2
  • #12 vte_terminal_insert_char
    from /usr/lib/libvte.so.2
  • #13 vte_terminal_process_incoming
    from /usr/lib/libvte.so.2
  • #14 g_idle_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main
  • #21 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6 






Comment 1


Elijah Newren





          2002-12-03 06:01:30 UTC
        




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