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 326551 - gnomeicu crashes if clicked on history with a single big msg in it
gnomeicu crashes if clicked on history with a single big msg in it
Status: RESOLVED FIXED
Product: GnomeICU
Classification: Deprecated
Component: General
0.99
Other All
: High major
: 1.0
Assigned To: gnomeicu-maint
gnomeicu-maint
Depends on:
Blocks:
 
 
Reported: 2006-01-10 23:46 UTC by Lukas Geyrhofer
Modified: 2006-10-09 07:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Lukas Geyrhofer 2006-01-10 23:46:54 UTC 
Steps to reproduce:
1. send a really big single msg to another user (sry, dont know how big it
actually was, cant view history :/ )
2. click on history of this user at any time - gnomeicu crashes instantly
3. 


Stack trace:


Other information:
Comment 1 Olivier Crête 2006-02-15 02:24:24 UTC 
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it.
Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Could you also run gnomeicu in a terminal and paste any output that it give there ?
Comment 2 Lukas Geyrhofer 2006-02-21 20:10:36 UTC 
stack trace:

[New Thread 16384 (LWP 18213)]
0xb783e2a8 in waitpid () from /lib/libpthread.so.0

+ Trace 66384

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 __pthread_sighandler
    from /lib/libpthread.so.0
  • #4 <signal handler called>
  • #5 rawmemchr
    from /lib/libc.so.6
  • #6 _IO_list_resetlock
    from /lib/libc.so.6
  • #7 ??
  • #8 _IO_init
    from /lib/libc.so.6 

i also tried to run it in the console, but there was no output which could be relevant for this error.
PS: currently i'm running version 0.99.10
Comment 3 Olivier Crête 2006-02-21 20:20:01 UTC 
history is in ~/.icq/UIN.txt (where UIN is the UIN ;) ... if you want to read it... And can you check how big the message was?
Comment 4 Lukas Geyrhofer 2006-02-21 21:09:45 UTC 
the message had 53728 characters (i was just copying&pasting stupid text ...)
Comment 5 Olivier Crête 2006-10-09 07:10:24 UTC 
Thanks, the history parsing code was really messy.. rewrote it.. now it should work fine for this case. Fix is in CVS, will be in the next version