From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13547 invoked by alias); 17 Dec 2002 01:22:48 -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 13530 invoked from network); 17 Dec 2002 01:22:47 -0000 Received: from unknown (HELO hqmail03.powertv.com) (140.174.253.39) by sources.redhat.com with SMTP; 17 Dec 2002 01:22:47 -0000 Received: from hqmail01.powertv.com ([204.182.4.208]) by hqmail03.powertv.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 16 Dec 2002 17:24:42 -0800 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Breakpoint and static functions Date: Mon, 16 Dec 2002 17:22:00 -0000 Message-ID: <762C0A863A7674478671627FEAF584812D798B@hqmail01.powertv.com> Importance: normal Priority: normal X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Cheng, Cheuk" To: X-OriginalArrivalTime: 17 Dec 2002 01:24:42.0056 (UTC) FILETIME=[131D3480:01C2A56B] X-SW-Source: 2002-12/txt/msg00230.txt.bz2 Hi, I am new to GDB and am having problem with the following. I am using a propietary OS running from ROM on an usparc based embedded system. This OS has a GDB nub (written in C and inline assembly) in it. Here is what I do. - Boot up usparc hardware containing debug build of OS in ROM. - set up GDB remote debug link from my PC to the hardware. - Enter "file osdebug.cof" at GDB prompt. - Enter "add-symbol-file application.cof " at GDB prompt. - Enter "target rem com1" at GDB prompt. - Enter command to load application into RAM inside a PC terminal program. Wait for it to finish loading. - Enter command inside PC terminal program to tell the OS to break into GDB. - Enter "b " at GDB prompt. Continue application execution. - GDB breaks at . Enter "continue" to go on. - GDB returns "Program received signal SIGTRAP, Trace/breakpoint trap." Now even after I use the "delete" command to remove the breakpoint, if I "continue" GDB will still break at the same spot. Using the "clear" command does not help too. - Now if I change the source code of the application to make the function non-static (by removing "static" in the function prototype and rebuild the application binary), then the above message will still appear (and the line number indicated by this message is still a few lines before where I originally set the breakpoint, e.g. b <> was at 9874 while the message indicated break at 9871"). However after I "delete" the original breakpoint, the message appears once and then I can "continue" one more time and no more stopping from now on. Am I doing something wrong in GDB? Or can that be our GDB nub inside the OS is bad (although I can always use the "list" command to view any source module without any problem)? Or is the use of static function with GDB problematic? Is it sufficient to have a GDB nub linked into the OS which is running from ROM or the application has to have its own GDB nub? Thanks. - - - - - - - Appended by PowerTV, Inc. - - - - - - -=20 This e-mail and any attachments may contain information that is confidentia= l, proprietary, privileged or otherwise protected by law. The information i= s solely intended for the named addressee (or a person responsible for deli= vering it to the addressee). If you are not the intended recipient of this = message, you are not authorized to read, print, retain, copy or disseminate= this message or any part of it. If you have received this e-mail in error,= please notify the sender immediately by return e-mail and delete it from y= our computer.