From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27392 invoked by alias); 13 Jun 2003 14:24:00 -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 27363 invoked from network); 13 Jun 2003 14:23:59 -0000 Received: from unknown (HELO mail.drexel.edu) (144.118.25.40) by sources.redhat.com with SMTP; 13 Jun 2003 14:23:59 -0000 Received: from webmail.drexel.edu (webmail.drexel.edu [144.118.25.20]) by mail.drexel.edu (Sun Internet Mail Server sims.4.0.2001.07.26.11.50.p9) with ESMTP id <0HGF00KFQBZVIK@mail.drexel.edu> for gdb@sources.redhat.com; Fri, 13 Jun 2003 10:23:56 -0400 (EDT) Date: Fri, 13 Jun 2003 14:24:00 -0000 From: nak26 Subject: RE: remote debugging To: Brijesh Shukla , Quality Quorum Cc: gdb Message-id: <3EE9CAB7@webmail.drexel.edu> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-WebMail-UserID: nak26 X-EXP32-SerialNo: 00003005 X-SW-Source: 2003-06/txt/msg00248.txt.bz2 >> gdb> load > >You should not do that, gdbserver already loaded the program. >The rest of your problems may be related to this step. > What works for me is 1.) gdb> file executable_name --That, of course, works if you built the executable locally, and also have access --to the code 2.) gdb> break break_point_somewhere 3.) gdb> continue --Don't do run, since gdbserver has already fired the process (on the remote --machine). --Nik