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 134196 - Occasional crash if terminal displays binary data
Occasional crash if terminal displays binary data
Status: RESOLVED DUPLICATE of bug 89541
Product: gnome-terminal
Classification: Core
Component: general
2.4.x
Other Linux
: Normal critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-02-12 10:09 UTC by Stephen Brooks
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4


Description Stephen Brooks 2004-02-12 10:09:17 UTC 
Description of Problem:


Steps to reproduce the problem:
1. 'more' a binary file within terminal
2. 
3. 

Actual Results:
Gnome-terminal crashes with a segmentation fault.

Expected Results:
Gracefully handle display of non-text bytes.

How often does this happen? 
Not 100% reproducible, happens about 1 in 10 times.

Additional Information:
I generally don't purposfully 'more' binary files but it does happen by
accident every now and then!

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 -1084951904 (LWP 2682)]

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

+ Trace 44096

Thread 1 (Thread -1084951904 (LWP 2682))

  • #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 






Comment 1


Mariano Suárez-Alvarez





          2004-02-12 16:54:58 UTC
        




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