From mboxrd@z Thu Jan  1 00:00:00 1970
From: Elena Zannoni <ezannoni@cygnus.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: completion.exp: what is "a64l"?
Date: Wed, 01 Aug 2001 18:53:00 -0000
Message-id: <15208.46214.493789.608207@krustylu.cygnus.com>
References: <3B68927F.64EE5475@cygnus.com>
X-SW-Source: 2001-08/msg00021.html

Michael Snyder writes:
 > Hi, 
 > 
 > The gdb test "completion.exp" is failing for me because 
 > it is expecting to see a symbol whose name begins with
 > "a64l" -- what is that?  There's no explanation for why
 > it should be expected to be there, or why its absence
 > amounts to a failure for gdb.
 > 
 > Michael

I was working on solaris at the time, so maybe that's what happens there.
Frankly I don't remember. :-(

I am rebuilding a solaris gdb at the moment.

.....

Ok, I see what I was trying to do:

The output of that test from gdb is a list of possible completions.
I was trying to match on the last line of the output (on solaris):

p 'a
a0		a7	  acosh		alarm	    ascftime	 atexit
a1		a8	  add		ald	    asctime	 atof
a10		a9	  add_concell  aldst	    asctime_r	 atoi
a11		aT	  adddays	allocid	    asin	 atol
a2		abort	  additem	allocstatic  asinh	 atoll
a3		abs	  addsev	almhdlr	    atan	 awake
a4		access	  addseverity  altzone	    atan2	
a5		acct	  adjtime	append	    atanh	 
a6		acl	  adjustwcptr  argc	    atanhi	 
a64l		acos	  advance	argv	    atanlo	 
(gdb) p 'a


So yes, my bad. Feel free to change it. Making sure we get some of the
'a' symbols in break.c before the gdb prompt is probably good enough,
those symbols should always be found.

Elena