From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20226 invoked by alias); 17 Feb 2008 19:47:53 -0000 Received: (qmail 20217 invoked by uid 22791); 17 Feb 2008 19:47:53 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 17 Feb 2008 19:47:36 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m1HJlX93004543; Sun, 17 Feb 2008 14:47:33 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m1HJlXUu022790; Sun, 17 Feb 2008 14:47:33 -0500 Received: from lindt.uglyboxes.com (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m1HJlWAq011285; Sun, 17 Feb 2008 14:47:33 -0500 Message-ID: <47B88F10.6060804@redhat.com> Date: Sun, 17 Feb 2008 19:47:00 -0000 From: Keith Seitz User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Geert Vancompernolle CC: Insight Foum Subject: Re: Run an external command prior to running the debugger References: <47B8789E.1010900@gmail.com> In-Reply-To: <47B8789E.1010900@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2008-q1/txt/msg00032.txt.bz2 Geert Vancompernolle wrote: > 1. start Insight > 2. start gdbserver on the target > 3. type "R" to run the software on the debugger. > > Is step 2 possible from within Insight? In other words: can I extend > the Insight command "R" such that it first launches the gdbserver on the > target and only then launches the debug session? Sort of, yes. It's kind of hacky, and I'm not entirely sure how well it will work, but there is an "After Attaching" preference in the Target Settings dialog (click the "More Options" widget-thingy). This will run any gdb command after attaching to the target. You could add something to use gdb's "shell" command to spawn your gdbserver. But like I said, I'm not sure how well that will work (or if it will work). My guess it has bitrotted... Keith