From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4457 invoked by alias); 29 May 2003 21:50:29 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 4424 invoked from network); 29 May 2003 21:50:29 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 29 May 2003 21:50:29 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3p2/8.9.3) with ESMTP id RAA30142 for ; Thu, 29 May 2003 17:45:36 -0400 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id RAA31823 for ; Thu, 29 May 2003 17:50:28 -0400 Message-ID: <00c001c3262c$5d880e40$0202040a@catdog> From: "Kris Warkentin" To: "Gdb@Sources.Redhat.Com" Subject: proposed solution for my remote 'run' problem Date: Thu, 29 May 2003 21:50:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003-05/txt/msg00405.txt.bz2 If anyone recalls, previously I had discussed a problem with our way of running things on the remote QNX machine. What we used to do is something like: (gdb) target qnx host:8000 (gdb) sym /path/to/some/host/file (gdb) b main (gdb) r /some/remote/path with some args This was considered ugly because it gave 'run' a context dependent definition: if exec_file is set, run just takes arguments, otherwise it takes a file and arguments. Today I just put in a string that can be set with 'set nto_remote_file'. Now if you call 'nto_create' (target_create_inferior), it will use this path if it is set, otherwise it will use the path passed in (which could be exec_file). This has the added benefit of letting you run gdb from the command line as 'gdb some_file'. Before, if you did that, exec_file would be set and you couldn't run the remote binary if its path was different than the host. So, if the paths are the same, it works normally, otherwise, you can set the remote binary but either way, exec_file doesn't affect things. Two problems I've observed with this approach. One: for some reason, when I run the program, it always says: 'some_program' has changed; re-reading symbols. I haven't chased this yet but it's kind of weird. Two: the target_create_inferior command doesn't take a 'from_tty' argument. It would be really nice if it did because I'd like to have output like so: Starting program: /cygdrive/k/test/float.x86 Remote: /home/kewarken/61/test/float.x86 Where the 'Remote' part comes from target_create_inferior. Can anyone suggest another place which has a 'from_tty' that I could put that message? If not, would anyone object to me changing all the target_create_inferiors to take a from_tty? cheers, Kris