QDevelop won't work

Bug #336692 reported by Tchokurov A.G.
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
qdevelop (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: qdevelop

I installed QDevelop with aptitude from jaunty-packages.

It starts, compiling the project, but when I try to edit the project files (cpp, h) hangs.

Files outside the project opens correctly.

description: updated
description: updated
Revision history for this message
Dmitry Tantsur (divius) wrote :

Please:
1) Provide your version of QDevelop as aptitude or synaptic shows it (note that the upstream doesn't support versions older than 0.26.1+svn090210).
2) Try using the latest code from the upstream (qdevelop.org)
3) Provide your project file (*.pro) on which QDevelop crashes.
4) Run QDevelop under gdb:
 a) First compile qdevelop from source using commands:
  $ qmake QDevelop.pro -after CONFIG+=debug
  $ make
 b) Install gdb, run:
  $ gdb bin/qdevelop
  (replace "bin/qdevelop" with path to qdevelop executable you've just compiled)
 c) Work with qdevelop until it hangs or crushes. If it hangs go to console from where you've started qdevelop and press ctrl+c to abort executing.
 d) You've see gdb's message about errors. Type:
  $ back
  You'll get backtrace. Please provide it here.

Revision history for this message
sasha1024 (sasha1024) wrote :

I confirm this -- for KUbuntu Jaunty Alpha6 (however, it worked fine for me on Intrepid).
The following happens: I can open old projects or create new. I can compile them. But when I double-click on some cpp or header file in the project, QDevelop hangs.

Revision history for this message
sasha1024 (sasha1024) wrote :

I'm not a reporter, but I can answer some of your questions:
1) Provide your version of QDevelop
0.26.1+svn090210-0ubuntu1

2) Try using the latest code from the upstream (qdevelop.org)
Yes, when I manually compile sources of 0.27 (stable) -- IT WORKS. (On the other hand, the so called "Linux dynamic version with plugins" (i.e. http://qdevelop.org/public/release/qdevelop-0.27-3-bin.tar.gz) hangs the same as jaunty-packaged version.)

3) Provide your project file (*.pro) on which QDevelop crashes.
At first, it doesn't crashes -- it _hangs_. At second, this happens on any projects, including newly-created. I.e. just do Menu/Project/NewProject/EmptyOrMasterProject/OK, then RightClick/AddNewItem/OK/Yes, then double-click newfile.cpp -- and it hangs.

I'll answer other questions later (no possibility right now).

sasha1024 (sasha1024)
Changed in qdevelop:
status: New → Confirmed
Revision history for this message
Dmitry Tantsur (divius) wrote :

Thus can we decide that it's a packaging problems? (I'm interested in it because I'm upstream member.)
"Linux dynamic version with plugins" can fail because it was linked against Qt 4.4.3.

But I'd like to see a backtrace first.

Revision history for this message
Tchokurov A.G. (me-ximik) wrote :

alex@laptop:~$ gdb qdevelop/bin/qdevelop
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(gdb) start
Breakpoint 1 at 0x80e4ff1
Starting program: /home/alex/qdevelop/bin/qdevelop
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bb2700 (LWP 10157)]
[Switching to Thread 0xb6bb2700 (LWP 10157)]
0x080e4ff1 in main ()
Current language: auto; currently asm
(gdb)

But there is now app window (or I make something wrong?)

Revision history for this message
Dmitry Tantsur (divius) wrote :

Do "run" instead of "start"

Revision history for this message
Tchokurov A.G. (me-ximik) wrote :

$ gdb bin/qdevelop
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(gdb) run
Starting program: /home/alex/qdevelop/bin/qdevelop
[Thread debugging using libthread_db enabled]
[New Thread 0xb6ba3700 (LWP 4405)]
[New Thread 0xb5e64b90 (LWP 4408)]
[New Thread 0xb55c5b90 (LWP 4413)]
[Thread 0xb55c5b90 (LWP 4413) exited]
[New Thread 0xb55c5b90 (LWP 4414)]
[Thread 0xb55c5b90 (LWP 4414) exited]

Then when I try to open file, qdevelop hangs and there is nothing new in console.

Revision history for this message
Dmitry Tantsur (divius) wrote :

As I've already written:

If it hangs go to console from where you've started qdevelop and press ctrl+c to abort executing.
 d) You've see gdb's message about errors. Type:
  $ back
  You'll get backtrace. Please provide it here.

Revision history for this message
Tchokurov A.G. (me-ximik) wrote :
Download full text (6.5 KiB)

^C
Program received signal SIGINT, Interrupt.
[Switching to Thread 0xb6af5700 (LWP 5582)]
0xb7229994 in ?? () from /usr/lib/libQtCore.so.4
(gdb) back
#0 0xb7229994 in ?? () from /usr/lib/libQtCore.so.4
#1 0xb7229dca in ?? () from /usr/lib/libQtCore.so.4
#2 0xb72311b3 in QRegExp::indexIn () from /usr/lib/libQtCore.so.4
#3 0xb7237f3a in QString::indexOf () from /usr/lib/libQtCore.so.4
#4 0x080b15a6 in CppHighlighter::doRegexMatch ()
#5 0x080c2a3e in CppHighlighter::highlightBlock ()
#6 0xb790b2bb in ?? () from /usr/lib/libQtGui.so.4
#7 0xb790b46d in ?? () from /usr/lib/libQtGui.so.4
#8 0xb790b7a4 in QSyntaxHighlighter::qt_metacall () from /usr/lib/libQtGui.so.4
#9 0xb72fccb8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb72fd942 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7cef6ff in QTextDocument::contentsChange () from /usr/lib/libQtGui.so.4
#12 0xb78ca644 in ?? () from /usr/lib/libQtGui.so.4
#13 0xb78f6424 in QTextCursor::endEditBlock () from /usr/lib/libQtGui.so.4
#14 0xb788a354 in ?? () from /usr/lib/libQtGui.so.4
#15 0xb788a6fb in QTextControl::setPlainText () from /usr/lib/libQtGui.so.4
#16 0xb7af0332 in QTextEdit::setPlainText () from /usr/lib/libQtGui.so.4
#17 0x0819231e in TextEdit::open () ...

Read more...

Revision history for this message
Dmitry Tantsur (divius) wrote :

I've already encountered this problem. It seems to be some Qt library incompatibility.

Revision history for this message
Andreas Wenning (andreas-wenning) wrote :

A new upstream version has just been uploaded to jaunty. Please test if this doesn't fix the problem?

Changed in qdevelop (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Tchokurov A.G. (me-ximik) wrote :

Yes, it works good.

Revision history for this message
Andreas Wenning (andreas-wenning) wrote :

Sounds good. Thanks a lot for reporting back.

Changed in qdevelop (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.