From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Engster Newsgroups: gmane.emacs.devel Subject: Re: progmodes/project.el and search paths Date: Mon, 03 Aug 2015 23:33:25 +0200 Message-ID: <87mvy8ys4a.fsf@isaac.fritz.box> References: <55BE209F.1000009@siege-engine.com> <55BE509B.2080307@yandex.ru> <87r3nkjxby.fsf@isaac.fritz.box> <55BF7619.1050701@yandex.ru> <87mvy8jvlh.fsf@isaac.fritz.box> <86lhdsfhz4.fsf@stephe-leake.org> <83zj28tj5q.fsf@gnu.org> <86a8u8f5dm.fsf@stephe-leake.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1438637643 31907 80.91.229.3 (3 Aug 2015 21:34:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 3 Aug 2015 21:34:03 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stephen Leake Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 03 23:33:52 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZMNMl-0006WO-2c for ged-emacs-devel@m.gmane.org; Mon, 03 Aug 2015 23:33:51 +0200 Original-Received: from localhost ([::1]:60561 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMNMk-0005Qa-H8 for ged-emacs-devel@m.gmane.org; Mon, 03 Aug 2015 17:33:50 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56330) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMNMX-0005QV-CP for emacs-devel@gnu.org; Mon, 03 Aug 2015 17:33:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZMNMT-0001pm-Tq for emacs-devel@gnu.org; Mon, 03 Aug 2015 17:33:37 -0400 Original-Received: from randomsample.de ([5.45.97.173]:59930) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMNMT-0001pY-Ks for emacs-devel@gnu.org; Mon, 03 Aug 2015 17:33:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=randomsample.de; s=a; h=Content-Type:MIME-Version:Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From; bh=CD2SBE0A/xvQg9R4C0HSaFHg5VdC32ySXxV1xcFfNk8=; b=K0oPHhuVfQNtwEUw22H3hLXwJp7Q9jGzgJesb1InkEI9VLSEGaiwH83qGzoOuN67hbqUKDGKobLWIBkyMnqrjwzfEiwalJO5MW0dR3bxZ4ZUfN5ytF1s6lxLGhOivfYc; Original-Received: from ip4d145d5e.dynamic.kabel-deutschland.de ([77.20.93.94] helo=isaac.fritz.box) by randomsample.de with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1ZMNMS-0004zp-5b; Mon, 03 Aug 2015 23:33:32 +0200 In-Reply-To: <86a8u8f5dm.fsf@stephe-leake.org> (Stephen Leake's message of "Mon, 03 Aug 2015 16:07:17 -0500") User-Agent: Gnus/5.13001 (Ma Gnus v0.10) Emacs/24.4 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 5.45.97.173 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:188371 Archived-At: Stephen Leake writes: > In addition, when I build things in makefiles, gud does a good job of > guessing the correct user executable, and the others are available thru > file completion (since they are all in the same directory). Not for me. Executables are all over the place and I always have to make sure I switch to the correct directory first. Gud frequently guesses wrong, probably because we have a very complicated parallel build. Also, I frequently have to switch between debugging locally and remotely on the target platform through gdbserver. > I don't see how a project can do better; there will still be a list of > possible executables; the most recently compiled isn't necessarily the > one I want to debug. Well, let's take Eclipse. It automatically scans the tree for binaries which you can quickly select for debugging. You can define different debug configurations where you can define the debugger to use, how it should be called and with which init file, if and where it should stop execution on startup, which executable it should debug and what arguments and environment it should provide, and if maybe this executable should be copied to a target system and debugged through gdbserver... And that's just what *I* regularly use. -David