From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11828 invoked by alias); 30 Sep 2011 18:15:19 -0000 Received: (qmail 11811 invoked by uid 22791); 30 Sep 2011 18:15:15 -0000 X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-ey0-f169.google.com (HELO mail-ey0-f169.google.com) (209.85.215.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 30 Sep 2011 18:14:46 +0000 Received: by eye13 with SMTP id 13so1548174eye.0 for ; Fri, 30 Sep 2011 11:14:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.16.70 with SMTP id n6mr3923eba.108.1317406485208; Fri, 30 Sep 2011 11:14:45 -0700 (PDT) Received: by 10.213.10.84 with HTTP; Fri, 30 Sep 2011 11:14:45 -0700 (PDT) In-Reply-To: References: Date: Fri, 30 Sep 2011 18:15:00 -0000 Message-ID: Subject: Re: command-list does not work in my gdb 7.2 port From: Liang Cheng To: Triple Yang Cc: Hui Zhu , gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-09/txt/msg00141.txt.bz2 He probably means you can try the latest gdb release as he did not see such an issue. On Tue, Sep 27, 2011 at 2:06 AM, Triple Yang wrote: > sorry, I do not understand what you are trying to say. > > 2011/9/27 Hui Zhu : >> (gdb) b mainBreakpoint 1 at 0x40056c: file 1.c, line 3.(gdb) commands >> Type commands for breakpoint(s) 1, one per line.End with a line saying >> just "end".>shell echo 123>end(gdb) rStarting program: >> /home/teawater/gdb/a.out >> Breakpoint 1, main () at 1.c:33 {123 >> Please try the trunk. >> >> Best, >> Hui >> https://code.google.com/p/gdbt/ >> >> On Mon, Sep 26, 2011 at 22:58, Triple Yang wrote: >>> Hi, everyone. >>> >>> I am making a gdb 7.2 port recently for a prototype architecture, >>> which is a remote debug target in my case. The port is almost done to >>> achieve my purposes, say: >>> >>> 1. Connecting to remote target and loading program image work well. >>> 2. Control on the debugged program is OK. >>> 3. Inserting/deleting breakpoints OK. >>> 4. and so as some other basic facilities. >>> >>> But when I tried using gdb command "commands" to specify a command >>> list after I set a breakpoint, I found this did not work at all. Here >>> follows a rough example: >>> >>> (gdb) break main >>> (gdb) commands >>>>shell echo test-commands >>>>end >>> (gdb) run >>> >>> In this example, the command list is composed of only one command >>> "shell echo test-commands". "test-commands" is expected to be output >>> when the breakpoint is hit, but it does not happen. I tried replacing >>> "shell echo test-commands" with other similar commands, it still did >>> not work. but "shell echo" does work well when it is not used in a >>> command list defined by "commands". >>> >>> I am not able to find any clue for this situation. Still worse, I can >>> not provide sufficient information to gdb experts for analysis. >>> >>> I am hoping that someone who has ever met this problem before can help >>> me with his/her invaluable suggestions. >>> >>> Thank you and best regards. >>> >>> -- >>> Yang Yong-Yong >>> >> > > > > -- > Yang Yong-Yong >