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 472641 - crash in Anjuta IDE: adding plugins to Anjuta...
crash in Anjuta IDE: adding plugins to Anjuta...
Status: RESOLVED DUPLICATE of bug 325759
Product: anjuta
Classification: Applications
Component: unknown
2.2.0
Other All
: High critical
: ---
Assigned To: Anjuta maintainers
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-01 20:31 UTC by uzi
Modified: 2007-09-02 16:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description uzi 2007-09-01 20:31:53 UTC 
What were you doing when the application crashed?
adding plugins to Anjuta 2.2.0


Distribution: Mandriva Linux release 2007.0 (Official) for i586
Gnome Release: 2.16.0 2006-09-04 (Mandriva)
BugBuddy Version: 2.16.0

Memory status: size: 59568128 vsize: 0 resident: 59568128 share: 0 rss: 30998528 rss_rlim: 0
CPU usage: start_time: 1188678473 rtime: 0 utime: 850 stime: 0 cutime:776 cstime: 0 timeout: 74 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/i686/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1226758464 (LWP 9723)]
0xbfffe410 in __kernel_vsyscall ()

+ Trace 159698

Thread 1 (Thread -1226758464 (LWP 9723))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/libc.so.6
  • #6 abort
    from /lib/i686/libc.so.6
  • #7 IA__g_logv 






Comment 1


Pascal Terjan





          2007-09-02 16:09:11 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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