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 357642 - crash in Gossip Instant Messenger:
crash in Gossip Instant Messenger:
Status: RESOLVED DUPLICATE of bug 346994
Product: gossip
Classification: Deprecated
Component: General
0.16
Other All
: High critical
: ---
Assigned To: Gossip Maintainers
Gossip Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-25 16:45 UTC by Aredridel
Modified: 2006-09-25 17:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Aredridel 2006-09-25 16:45:06 UTC 
What were you doing when the application crashed?



Distribution: Unknown
Gnome Release: 2.16.0 2006-09-04 (PLD Linux Distribution)
BugBuddy Version: 2.15.92

Memory status: size: 28807168 vsize: 0 resident: 28807168 share: 0 rss: 18022400 rss_rlim: 0
CPU usage: start_time: 1159202635 rtime: 0 utime: 185 stime: 0 cutime:177 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gossip'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 73218

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_type_check_instance_cast
    from /usr/lib/libgobject-2.0.so.0
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 pthread_mutex_timedlock
    from /lib/libpthread.so.0
  • #9 g_source_remove
    from /usr/lib/libglib-2.0.so.0
  • #10 ??
  • #11 ??
  • #12 ?? 






Comment 1


Richard Hult





          2006-09-25 17:01:50 UTC
        



Marking as dup of the lm crasher, note that the trace doesn't look the same, but there are a few different variants of it that happens depending on where the memory corruption happens to hit.

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