From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10805 invoked by alias); 18 Feb 2002 23:46:37 -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 10661 invoked from network); 18 Feb 2002 23:46:21 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 18 Feb 2002 23:46:21 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id g1INkKQ29986; Mon, 18 Feb 2002 17:46:20 -0600 Date: Mon, 18 Feb 2002 15:46:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200202182346.g1INkKQ29986@duracef.shout.net> To: keiths@redhat.com Subject: Re: how to call gdb_test "" ... ? Cc: gdb@sources.redhat.com X-SW-Source: 2002-02/txt/msg00237.txt.bz2 Keith Seitz writes: > Actually, I don't see from reading the code for gdb_test why "" would be > disallowed. Is it giving you some sort of error? gdb_test "" hangs and does not return until some 60-second timer kicks it out. That's probably related to the special check for "": set result -1 set string "${command}\n"; if { $command != "" } { ... } Hmmm, this is actually documented behavior: # COMMAND is the command to execute, send to GDB with send_gdb. If this is the null string no command is sent. I suppose I could do this: send_gdb "\n" gdb_test "" "..." How does that sound, Keith? Or would you prefer me to stick with send_gdb/gdb_expect? Gross choice, eh? I can't modify gdb_test; that would take me too far afield from fixing the real problems in list.exp. Michael C