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 538635 - crash in Anjuta IDE: Anjuta freeze on run pro...
crash in Anjuta IDE: Anjuta freeze on run pro...
Status: RESOLVED DUPLICATE of bug 538344
Product: anjuta
Classification: Applications
Component: unknown
2.4.x
Other All
: High critical
: ---
Assigned To: Anjuta maintainers
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-16 15:59 UTC by dr-ru
Modified: 2008-06-20 19:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description dr-ru 2008-06-16 15:59:49 UTC 
Version: 2.4.2

What were you doing when the application crashed?
Anjuta freeze on run program in terminal


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-amd64 #1 SMP Thu Jun 12 15:38:32 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 323686400 vsize: 323686400 resident: 42700800 share: 18755584 rss: 42700800 rss_rlim: 18446744073709551615
CPU usage: start_time: 1213631237 rtime: 158 utime: 138 stime: 20 cutime:27 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f37ea876780 (LWP 13406)]
[New Thread 0x41030950 (LWP 13500)]
(no debugging symbols found)
0x00007f37e573d7db in read () from /lib/libpthread.so.0

+ Trace 200583

Thread 2 (Thread 0x41030950 (LWP 13500))

  • #0 read
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libglib-2.0.so.0
  • #2 ??
    from /usr/lib/libglib-2.0.so.0
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 1 (Thread 0x7f37ea876780 (LWP 13406))

  • #0 read
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libvte.so.9
  • #2 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 ??
  • #7 __libc_start_main
    from /lib/libc.so.6
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #0 read
    from /lib/libpthread.so.0 


----------- .xsession-errors (168 sec old) ---------------------
    Vim: 
OPENING /home/dr/Projects/foo-bars/autogen.sh as Sh language file
OPENING /home/dr/Projects/foo-bars/autogen.sh as Sh language file
OPENING /home/dr/Projects/foo-bars/config.h as C++ language file
OPENING /home/dr/Projects/foo-bars/ltmain.sh as Sh language file
OPENING /home/dr/Projects/foo-bars/ltmain.sh as Sh language file
OPENING /home/dr/Projects/foo-bars/src/main.cc as C++ language file
OPENING /home/dr/Projects/foo-bars/config.h as C++ language file
OPENING /home/dr/Projects/foo-bars/src/main.cc as C++ language file
OPENING /home/dr/Projects/foo-bars/src/main.cc as C++ language
(anjuta:13406): libanjuta-WARNING **: Failed to synchronize plugins profile 'project': Файл не найден
(anjuta:13406): libanjuta-WARNING **: Failed to synchronize plugins profile 'project': Файл не найден
Предупреждение менеджера окон: last_user_time (1616012928) is greater than comparison timestamp (3337385).  This most likely represents a buggy client sending inaccurate tim
Предупреждение менеджера окон: 0x3c00081 (Synaptic) appears to be one of the offending windows with a timestamp of 1616012928.  Working around...
--------------------------------------------------
Comment 1 Johannes Schmid 2008-06-16 16:14:25 UTC 
Backtrace is missing but I guess it's a duplicate of bug 538344.

Are you using a very recent version of libvte?

Thanks!
Comment 2 dr-ru 2008-06-17 14:21:52 UTC 
(In reply to comment #1)
> Backtrace is missing but I guess it's a duplicate of bug 538344.
> 
> Are you using a very recent version of libvte?
> 
> Thanks!
> 

Im use debian sid and libvte.so.9.2.18
Comment 3 Sébastien Granjoux 2008-06-20 19:02:01 UTC 
(In reply to comment #2)
> Im use debian sid and libvte.so.9.2.18

I have libvte.so.9.2.17 which correspond to vte 0.16.13, while libvte.so.9.2.18 correspond to vte 0.16.14.

According to the information in bug 538344, this bug is due to change 2041 which has been committed between vte 0.16.13 and vte 0.16.14.

So you get it and it's a duplicate of bug 538344, anyway thanks for reporting this.

 



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