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 306582 - Anjuta crashes when typing "std::"
Anjuta crashes when typing "std::"
Status: VERIFIED FIXED
Product: anjuta
Classification: Applications
Component: core application
2.0.x
Other other
: Normal normal
: ---
Assigned To: Anjuta maintainers
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-05 20:27 UTC by ceacy
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description ceacy 2005-06-05 20:27:29 UTC 
Distribution: Debian 3.1
Package: anjuta
Severity: normal
Version: GNOME2.10.0 2.0.x
Gnome-Distributor: Ubuntu
Synopsis: Anjuta crashes when typing "std::"
Bugzilla-Product: anjuta
Bugzilla-Component: core application
Bugzilla-Version: 2.0.x
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
Anjuta 2.0.0 crashed when i typed "std::" in a file.

Steps to reproduce the crash:
1. 
2. 
3. Type "std::" somewhere.

Expected Results:
Just after the second ":", Anjuta crashes.

How often does this happen?
After the first time it happened : each time i typed "std::".

Additional Information:
This bug only appeared after a few hours using Anjuta 2.0.0.


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1222164352 (LWP 31797)]
[New Thread -1238369360 (LWP 31803)]
[New Thread -1236935760 (LWP 31802)]
[New Thread -1228543056 (LWP 31801)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 60581

Thread 4 (Thread -1228543056 (LWP 31801))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_loop_get_context
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-05 20:27 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was ceacy@wanadoo.fr.
Comment 1 Naba Kumar 2005-06-18 13:30:02 UTC 
IIRC, something was fixed related to this. Can someone confirm whether this is
fixed or not?
Comment 2 Christian Kirbach 2005-06-19 23:05:29 UTC 
unique stack trace.
Comment 3 Marc Maurer 2006-05-20 12:00:27 UTC 
Can't reproduce with 2.0.2.
Comment 4 Johannes Schmid 2006-05-20 15:44:51 UTC 
Closing now because nobody can reproduce this. Feel free to reopen if the bug is still valid!
Comment 5 Naba Kumar 2006-12-04 09:59:44 UTC 
Closing all fixed bugs. Sorry for the mass update :( ...