From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2381 invoked by alias); 12 Dec 2002 18:20:56 -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 2373 invoked from network); 12 Dec 2002 18:20:54 -0000 Received: from unknown (HELO integraonline.com) (206.163.82.90) by sources.redhat.com with SMTP; 12 Dec 2002 18:20:54 -0000 Received: (qmail 1684 invoked from network); 12 Dec 2002 18:20:51 -0000 Received: from unknown (HELO ?192.168.0.83?) ([64.122.47.50]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 12 Dec 2002 18:20:51 -0000 Subject: Re: remote debugging From: Tim To: Keith Seitz Cc: insight@sources.redhat.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 12 Dec 2002 10:20:00 -0000 Message-Id: <1039717290.1418.75.camel@TIM.DCS> Mime-Version: 1.0 X-SW-Source: 2002-q4/txt/msg00193.txt.bz2 I am able to get everything going. Thanx for your help. I tried a few things... I used a gdbserver compiled statically against glibc from the insight directory tree rather than the uClibc version I was using. I changed the Run Method to Continue from Last Stop. I rebuilt my application. Once I changed the run method insight connected but gave a segmentation fault immediately. On the next try I changed both gdbserver and my application so I suspect that one of the two were out of sync, (the host version of my app and the remote version of my app more than likely). Thanx again!. On Thu, 2002-12-12 at 10:00, Keith Seitz wrote: > On 12 Dec 2002, Tim wrote: > > > 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. > > That's probably a long-standing bug... :-( It should never try to run > locally when cross-debugging. > > > I'm assuming that I'm doing something wrong and insight is not > > attempting to connect to the remote device. > > I don't think you're doing anything wrong, but let's see if we can't get > you going. > > > 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! > > Couple of bits of info will help us direct the investigation, so: > > What's the output of "gdb -v" (or "insight -v" if you've got a newer > version of insight)? > > What are the commands you use in the console to get this working? ("file > FOO", "break main", "target remote 192.168.0.29:2345", "continue", etc) > > Keith > > >