[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 100265] New: Custom Makefiles project, allow to debug another executable different from "Main P
From: kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date: 2005-02-25 17:04:22
Message-ID: 20050225180420.100265.j_blasi () wanadoo ! es
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=100265
Summary: Custom Makefiles project, allow to debug another
executable different from "Main Program".
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
AssignedTo: kdevelop-bugs kdevelop org
ReportedBy: j_blasi wanadoo es
Version: 3.1.92 [aka 3.2 beta 2] (using KDE KDE 3.2.3)
Installed from: Compiled From Sources
Compiler: gcc version 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)
OS: Linux
Assuming that you have an Imported Existing Project ... Custom Makefiles.
Add the ability to debug another executable different from the one you have \
configured in Project -> Project Options -> Run Options : "Main program"
That was possible in previous Kdevelop 2.x releases [Debug -> Start (other)...].
Keep in mind that large projects may build more than one executable. Then, is common \
to execute one while debugging another. Of course I do not want to change Project -> \
Project Options -> Run Options every time, I leave there the main one.
That issue applies also when you wish to "Attach to Process".
You should as well consider executing a binary different from the "Main program" \
configured in "Run Options", something like Build -> Execute (other) ... [and from \
toolbar also] capturing output in Application Output View or in external terminal as \
a choice.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic