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 [thread overview]
Message-ID: <15208.46214.493789.608207@krustylu.cygnus.com> (raw)
In-Reply-To: <3B68927F.64EE5475@cygnus.com>
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
next prev parent reply other threads:[~2001-08-01 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 16:40 Michael Snyder
2001-08-01 16:54 ` Daniel Berlin
2001-08-01 18:20 ` Andrew Cagney
2001-08-02 12:00 ` Michael Snyder
2001-08-02 12:29 ` Elena Zannoni
2001-08-02 15:59 ` Michael Snyder
2001-08-01 18:53 ` Elena Zannoni [this message]
2001-08-01 21:26 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15208.46214.493789.608207@krustylu.cygnus.com \
--to=ezannoni@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox