unable to debug if not started from project directory

[mehrwarz enayati]

Binary package hint: qdevelop

Ubuntu 8.04 Hardy

qdevelop:
  Installed: 0.25.2-0ubuntu1
  Candidate: 0.25.2-0ubuntu1
  Version table:
 *** 0.25.2-0ubuntu1 0
        500 file: hardy/universe Packages
        100 /var/lib/dpkg/status

Bug description:
If you start qdevelop from any directory but .pro file directory, breakpoint would not work. gdb would complaint that it could not find the specified files (main.cpp for example). I think this is due to wrong working directory for gdb and passing file names in relative form to gdb.

What I expected:
Being able to work with breakpoints while run qdevelop from any directory (from Development menu for example).

What happened instead:
Breakpoints dont work when I run qdevelop from a directory other than project src directory.

[Pablo Castellano (pablocastellano)]

Hello!
Could you please check if this issue is still happening with last svn version?
You can do it installing last Ubuntu Intrepid release since it provides last version available.
Thanks in advance.

[BHowell (mute-howell-ersatz)]

I can reproduce this behavior in 8.10 beta.

[xtknight (xt-knight)]

Ya this didn't happen in 8.04 but it happens in 8.10 final. None of my breakpoints work anymore.

[xtknight (xt-knight)]

Recompiled QDevelop with absolute path breakpoints and that didn't work. Then I tried it myself and realized the problem was deeper.

-g (write debug symbols) wasn't added to the make c/cxx flags in Makefile.

qmake bug? Something making Makefile is screwing up with the same QDevelop project file.

[xtknight (xt-knight)]

I don't know. I hadn't created my .pro file with QDevelop and there needs to be a "CONFIG += debug" in that file.

So I assume some sort of default changed and now qmake no longer puts -g in C/CXX FLAGS by default. That would explain it.

[Dmitry Tantsur (divius)]

I cannot reproduce this bug.
Of course you won't be able to use debugging if it's turned off!
With "CONFIG += debug" everything works for me.

[xtknight (xt-knight)]

Divius: the point is, it used to be fine. This is a regression.

On Tue, Jan 20, 2009 at 8:16 AM, Divius <email address hidden> wrote:

> I cannot reproduce this bug.
> Of course you won't be able to use debugging if it's turned off!
> With "CONFIG += debug" everything works for me.
>
> --
> unable to debug if not started from project directory
> https://bugs.launchpad.net/bugs/236880
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Dmitry Tantsur (divius)]

Ok, could you please provide exact steps to reproduce the problem, I'll test it.

[Andreas Wenning (andreas-wenning)]

Also a new upstream stable version 0.27.4 has been uploaded to jaunty; does this version behave the same for you?