List Info

Thread: Undebuggable crash




Undebuggable crash
country flaguser name
Germany
2008-02-28 21:14:17
Hi! Since my the commit I did today, I sometimes get a crash
in kdevelop while 
parsing, that I cannot debug. I simply cannot find out
what's causing it. Gdb 
does not give me a correct backtrace, and valgrind doesn't
too.

Maybe someone else has more luck?

What you need to do:
- Build current kdevelop-4
- Start kdevelop-4, and open the kdevelop-project itself.
- Make sure you have a cmake build-directory set up in
Settings -> Project -> 
KDevelop -> CMake, so the include-path resolver works.
- Open cpplanguagesupport.cpp
- Close kdevelop
- Start kdevelop
- cpplanguagesupport.cpp is automatically re-opened, wait
until parsing has 
finished
- Open the kdevelop project
- Wait until it is imported by cmake
- Insert a single space in the cpplanguagesupport.cpp file,
so it is reparsed.
- Wait for crash

Greetings, David

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

Re: Undebuggable crash
country flaguser name
Australia
2008-03-01 06:21:11
On Fri, 29 Feb 2008 02:14:17 pm David Nolden wrote:
> Hi! Since my the commit I did today, I sometimes get a
crash in kdevelop
> while parsing, that I cannot debug. I simply cannot
find out what's causing
> it. Gdb does not give me a correct backtrace, and
valgrind doesn't too.

Bad compile perhaps? Stale includes? etc.

Cheers,
Hamish.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

Re: Undebuggable crash
user name
2008-03-01 15:45:49
On 29.02.08 04:14:17, David Nolden wrote:
> Hi! Since my the commit I did today, I sometimes get a
crash in kdevelop while 
> parsing, that I cannot debug. I simply cannot find out
what's causing it. Gdb 
> does not give me a correct backtrace, and valgrind
doesn't too.
> 
> Maybe someone else has more luck?
> 
> What you need to do:
> - Build current kdevelop-4
> - Start kdevelop-4, and open the kdevelop-project
itself.
> - Make sure you have a cmake build-directory set up in
Settings -> Project -> 
> KDevelop -> CMake, so the include-path resolver
works.
> - Open cpplanguagesupport.cpp
> - Close kdevelop
> - Start kdevelop
> - cpplanguagesupport.cpp is automatically re-opened,
wait until parsing has 
> finished
> - Open the kdevelop project
> - Wait until it is imported by cmake
> - Insert a single space in the cpplanguagesupport.cpp
file, so it is reparsed.
> - Wait for crash

Doesn't crash for me (I'm assuming it doesn't crash if I'm
getting the
"parsing finished for cpplanguagesupport.cpp"
message).

However I'm not sure your steps are correct, because the
project is
automatically opened on the second start, so opening again
re-opens it
(which actually creates a second entry in the project tree,
which is a
bug obviously). And when you close the project before
closing kdevelop
for the first time, cpplanguagesupport.cpp is also
automatically closed.

Andreas

-- 
You may be infinitely smaller than some things, but you're
infinitely
larger than others.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

Re: Undebuggable crash
country flaguser name
Germany
2008-03-01 19:53:33
On Saturday 01 March 2008 13:21:11 Hamish Rodda wrote:
> Bad compile perhaps? Stale includes? etc.
>
> Cheers,
> Hamish.

I'll rebuild everything and see what happens.

Greetings, David

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

Re: Undebuggable crash
country flaguser name
Germany
2008-03-01 19:55:45
On Saturday 01 March 2008 22:45:49 Andreas Pakulat wrote:
> automatically opened on the second start, so opening
again re-opens it
> (which actually creates a second entry in the project
tree, which is a
> bug obviously). And when you close the project before
closing kdevelop
> for the first time, cpplanguagesupport.cpp is also
automatically closed.
>
> Andreas

I haven't ever seen kdevelop automatically re-load
previously opened projects, 
but maybe that part of kdevelop wasn't up to date.

Anyway I will rebuild everything, and probably this crash
won't happen again, 
because 4 people all weren't able to reproduce it.

Greetings, David

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

[1-5]

about | contact  Other archives ( Real Estate discussion Medical topics )