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 305249 - crash after hitting ctrl-c multiple times to stop grep from spewing binary data onto screen
crash after hitting ctrl-c multiple times to stop grep from spewing binary da...
Status: RESOLVED DUPLICATE of bug 107262
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-05-23 18:53 UTC by jeff
Modified: 2005-05-29 15:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4


Description jeff 2005-05-23 18:53:36 UTC 
Distribution: Fedora Core release 1 (Yarrow)
Package: gnome-terminal
Severity: normal
Version: GNOME2.4.0 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: crash after hitting ctrl-c multiple times to stop grep from spewing binary data onto screen
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:
grep spewed binary data, put terminal into graphics character mode, I
hit ctrl-c a lot, then it crashed

Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?
It may have happened before, I don't remember

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 -1084472672 (LWP 7673)]

(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)...0x002fbc32 in _dl_sysinfo_int80 ()
   from /lib/ld-linux.so.2

+ Trace 60084

Thread 1 (Thread -1084472672 (LWP 7673))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #5 eel_pango_layout_set_font_desc_from_string
  • #6 eel_pango_layout_set_font_desc_from_string
  • #7 eel_pango_layout_set_text_ellipsized
  • #8 eel_ellipsizing_label_set_text
  • #9 g_cclosure_marshal_VOID__BOXED
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-23 18:53 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was jeff@aurora.lxvi.net.
Comment 1 Elijah Newren 2005-05-29 15:49:42 UTC 
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

Matches the stack trace in bug 136362, which has been marked as a duplicate of
107262.

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