From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27321 invoked by alias); 12 Dec 2002 18:01:32 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 27286 invoked from network); 12 Dec 2002 18:01:23 -0000 Received: from unknown (HELO exchwenz01.smtp.dmcwave.co.nz) (202.27.34.1) by sources.redhat.com with SMTP; 12 Dec 2002 18:01:23 -0000 Received: by exchwenz01.dmcwave.co.nz with Internet Mail Service (5.5.2656.59) id ; Fri, 13 Dec 2002 07:01:21 +1300 Message-ID: <8D7C5F56B409554D9D46AC22195807F3061BD2@exchwenz01.dmcwave.co.nz> From: Rod Boyce To: 'Tim' Cc: insight@sources.redhat.com Subject: RE: remote debugging Date: Thu, 12 Dec 2002 10:01:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-SW-Source: 2002-q4/txt/msg00192.txt.bz2 All, This is how I do it. 1. run gdbserver of the target 2. Start insight 3. load the application you want to debug 4. set the target selection to remote TCP the host IP address and port you want to use. Make sure you download program is deselected and attach to target is selected. I also make sure there are not breakpoints set for me. Set breakpoint and main and at exit are deselected. 5. using the function browser under the view command place the breakpoint where you want to. I normall add one at the beginning of main here (I have control of where the breakpoint gets set some time not the beginning of main but before main or in a specific function to debug a specific feature. 6. Then I hit the run button. The program starts and continues until it hits my breakpoint. This works fine for me. I use a similar functionality with my BDI2000 or with gdbserver it depends on what I'm debugging. I have even used this kind of setup to debug the kernel, application and drivers all at the same time with source code level debugging. I love Insight it was the easiest for me to get going an while I'm getting to know the GDB command line Insight is a great way for us windows converts to get used to Linux. The Insight guys have done a great job. Keep up the good work. Regards, Rod Boyce. -----Original Message----- From: Tim [mailto:Tim@deltacompsys.com] Sent: Thursday, December 12, 2002 9:39 AM To: Keith Seitz Cc: insight@sources.redhat.com Subject: Re: remote debugging I understand using the open menu option, and that is what I tried. When 'run' the app after opening the local executable, there is no connection message on the remote device. What appears to be happening is that insight is running the application locally and not connecting to the remote device. I'm assuming that I'm doing something wrong and insight is not attempting to connect to the remote device. I set the target settings to: Target: Remote/TCP Hostname: 192.168.0.29 Port: 2345 Run Options: Attach To Target Run Method: Run Program when I run a console gdb it will connect, but insigt does not... Any help is appreciated. Thanx! On Thu, 2002-12-12 at 09:29, Keith Seitz wrote: > On 12 Dec 2002, Tim wrote: > > > Do I need to "Open" the executable in Insight? Once I do it executes > > locally and not remotely and the remote app often terminates with an > > error "Killing inferior". > > The Run button will always do whatever it needs (or thinks it needs) to > start the application "running" on your target. This includes: > > 1) opening an executable/debug file > 2) gathering target communications information (debug protocol/transport) > 3) loading executable into target memory (if needed) > 4) "running" the target > > If you don't "Open" an executable, how is the debugger to know what you > are debugging? It still needs debug symbols (or at least minimal symbols > from the executable). > > Keith > > >