Bug 566209 - "generate inhertances..." progress bar doesn't disappear
"generate inhertances..." progress bar doesn't disappear
Status: RESOLVED FIXED
Product: anjuta
Classification: Applications
Component: plugins: symbol-db
SVN TRUNK
Other Linux
: Normal normal
: ---
Assigned To: Massimo Cora'
Anjuta maintainers
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2009-01-01 16:52 UTC by Johannes Schmid
Modified: 2009-12-29 19:55 UTC (History)
0 users

See Also:
GNOME target: ---
GNOME version: ---


Attachments

Description Johannes Schmid 2009-01-01 16:52:41 UTC
After some work with the symbol-db it seems to end up in an inconsistent state and blocks when editing some text while searching for a symbol. Following backtrace appeared after 2 minutes of waiting. In some other cases I got criticals about g_value and gda_holder stuff.

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 _L_lock_89
    from /lib/tls/i686/cmov/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/tls/i686/cmov/libpthread.so.0
  • #4 symbol_db_engine_find_symbol_by_name_pattern_filtered
    at symbol-db-engine-queries.c line 2159
  • #5 isymbol_manager_search
    at plugin.c line 2387
  • #6 ianjuta_symbol_manager_search
    at ianjuta-symbol-manager.c line 246
  • #7 cpp_java_assist_check
    at cpp-java-assist.c line 451

In addition, the "generate inhertances..." progress bar doesn't disappear ever for global symbols.
Comment 1 Massimo Cora' 2009-01-01 17:55:01 UTC
(In reply to comment #0)
> After some work with the symbol-db it seems to end up in an inconsistent state
> and blocks when editing some text while searching for a symbol. Following
> backtrace appeared after 2 minutes of waiting. In some other cases I got
> criticals about g_value and gda_holder stuff.
> 

hmm please try to run with --g-fatal-warnings and let's see which point breaks.

> 
> In addition, the "generate inhertances..." progress bar doesn't disappear ever
> for global symbols.
> 

yeah I got that too, I'm investigating. AFAIK it seems to be only a graphical bug.
Comment 2 Massimo Cora' 2009-01-02 00:20:37 UTC
(In reply to comment #0)
> After some work with the symbol-db it seems to end up in an inconsistent state
> and blocks when editing some text while searching for a symbol. Following
> backtrace appeared after 2 minutes of waiting. In some other cases I got
> criticals about g_value and gda_holder stuff.
> 

I've done a code cleaning on the engine core which probably caused those warnings. Please check with new version if those still occur.
Comment 3 Massimo Cora' 2009-01-08 17:30:54 UTC
I'm not seeing Anjuta blocking anymore.
The but can be changed to "generate inhertances..." progress bar doesn't disappear.
Comment 4 Massimo Cora' 2009-01-31 01:32:11 UTC
(In reply to comment #3)
> I'm not seeing Anjuta blocking anymore.
> The but can be changed to "generate inhertances..." progress bar doesn't
> disappear.
> 

on trunk there's a version that should fix this.


Have you ever had a gui block while editing since this bug was filed?

Comment 5 Massimo Cora' 2009-01-31 10:58:00 UTC
maybe the locking was due to bug #568031.
Comment 6 Johannes Schmid 2009-02-26 07:52:17 UTC
Still happens sometimes but I have no sane way or reproducing!
Comment 7 Massimo Cora' 2009-12-29 15:23:04 UTC
I investigated this one.
And maybe I've found a way to reproduce it.

1. Open Anjuta.
2. Close all documents.
3. Close the active project.
4. Close any documents that remain opened.
5. Close Anjuta.
7. Open Anjuta. A fresh interface without documents nor symbo-db should come up.
8. Open a /tmp/foo_file.c 
9. Symbol-db gets loaded and two bars displayed.

This isn't correct and I'll try to fix this.
Anyway shouldn't project-manager take care of opening a foo project when no project nor files were stored on session?
Comment 8 Massimo Cora' 2009-12-29 19:55:48 UTC
I've committed a patch for this. The 'generating inheritances' messages was there I suppose because it was not cleared.

If you still encounter some weird behaviour please reopen this.

Note You need to log in before you can comment on or make changes to this bug.