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 346496 - gossip crashes when arriving unicode links
gossip crashes when arriving unicode links
Status: RESOLVED FIXED
Product: gossip
Classification: Deprecated
Component: General
unspecified
Other All
: Normal normal
: ---
Assigned To: Gossip Maintainers
Gossip Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-03 21:38 UTC by Keywan Najafi Tonekaboni
Modified: 2006-07-04 10:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Keywan Najafi Tonekaboni 2006-07-03 21:38:08 UTC
Please describe the problem:
I use gossip from cvs HEAD. When I arrive a link with non-ascii chars gossip crashes. 

Steps to reproduce:
1. Receive a message with a link like this: http://www.test.com/ä



Actual results:
Gossip crashes

Expected results:


Does this happen every time?
yes, also with í etc

Other information:
Backtrace was generated from '/opt/bleedingedge/bin/gossip'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 805560848 (LWP 26486)]
0x0ec21c58 in __waitpid_nocancel () from /lib/libpthread.so.0

Thread 1 (Thread 805560848 (LWP 26486))

  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_markup_escape_text
    from /usr/lib/libglib-2.0.so.0
  • #4 log_urlify
    at gossip-log.c line 997
  • #5 gossip_log_message_for_contact
    at gossip-log.c line 1569
  • #6 private_chat_input_key_press_event_cb
    at gossip-private-chat.c line 358
  • #7 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_window_propagate_key_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_window_activate_key
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #25 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #28 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 main
    at gossip-main.c line 182
  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0

Comment 1 Richard Hult 2006-07-04 07:07:12 UTC
Thanks! However, I can't reproduce this. It might depend on whether your regexp library supports utf8 or not. I don't think we need to keep the code that crashes though since it's a left-over from the old logging code. I will proabably just remove it after speaking to Martyn.
Comment 2 Keywan Najafi Tonekaboni 2006-07-04 07:37:11 UTC
I am not sure if this detail is important, but I use a PowerPC.

I haven't this problem with a cvs version from last week monday, but with
a cvs version from last friday. (I compile a new gossip from head of course, before I report the bug)

I also test it with gossip 0.10.2 and can't reproduce it there...




 
Comment 3 Richard Hult 2006-07-04 10:48:41 UTC
I removed that code, closing.