[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 120795] can only debug the main application
From:       Jens Dagerbo <jens.dagerbo () swipnet ! se>
Date:       2006-12-31 15:09:51
Message-ID: 20061231150951.6943.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=120795         
jens.dagerbo swipnet se changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |UNCONFIRMED



------- Additional Comments From jens.dagerbo swipnet se  2006-12-31 16:09 -------
This is confusing as hell, and always was.. but it does work, at least for automake \
projects.

1. Set a subproject active in the Automake Manager
2. Debug->Start
=> active target is started in debugger

Simple, right? Well.. the unexpected prerequisite:
Project -> Project Options -> Run Options -> Main Program - must be empty!

The "main program" entry acts as a override, probably in some misguided attempt to be \
user friendly, as the AM is apparently has to find..


For QMake based project, it at least used to be possible to have the QM return the \
currently selected node as the "active project", which would then let the debugger \
get the correct path to the binary. Don't know if this still works. Apaku?

I doubt it's possible for Custom Makefiles projects, but that's what bug #100265 is \
about.


[prev in list] [next in list] [prev in thread] [next in thread]