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 679772 - Deadlock when typing this-> with this specific project
Deadlock when typing this-> with this specific project
Status: VERIFIED FIXED
Product: anjuta
Classification: Applications
Component: plugins: symbol-db
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Massimo Cora'
Anjuta maintainers
: 680681 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-07-11 22:46 UTC by Lucas van Dijk
Modified: 2012-11-21 21:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Project with problems (825.94 KB, application/zip)
2012-07-11 22:46 UTC, Lucas van Dijk 		Details

Description Lucas van Dijk 2012-07-11 22:46:15 UTC 
Created attachment 218591 [details]
Project with problems

Hi guys,

I've attached a project with anjuta_sym_db.db where my anjuta keeps getting in a deadlock. Here on my home computer, everytime I type 'this->', and the symbol DB plugin queries the database, it somehow hangs. With GDB I saw it keeps waiting on a mutex to unlock, but I can't give any details.

Steps to reproduce:
- Open the anjuta project attachted
- Open the file tlc_controller.cpp
- Inside a function (for example, TLCController::sendDotCorrection), begin typing this->
- Deadlock

I hope the same happens when you open the project.
Comment 1 Johannes Schmid 2012-07-13 18:34:09 UTC 
Thanks for your detailed report, I will try to have a look at it soon.
Comment 2 Massimo Cora' 2012-07-13 23:52:23 UTC 
It was an infinite loop, not a mutex.
Anyway thanks for reporting it. I've just committed a patch on master that fixes the problem for me.

Can you please check if it's ok for you too?
Comment 3 Johannes Schmid 2012-07-28 09:34:17 UTC 
*** Bug 680681 has been marked as a duplicate of this bug. ***
Comment 4 Tobias Mueller 2012-11-21 13:58:20 UTC 
Massimo, do you remember which patch it was so that we can include that here for reference?

Anyway, I am closing as FIXED. Please reopen if this is not the case or set to VERIFIED if it does indeed fix the issue. Thanks.
Comment 5 Massimo Cora' 2012-11-21 21:15:21 UTC 
sure here it is http://git.gnome.org/browse/anjuta/commit/?id=32e59b87bde9f71cddb8d9e8d40f0020f698728a

I suppose that this can be considered fixed and verified, I'm not getting it anymore.
I'm setting verified.