From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb@sources.redhat.com
Subject: Re: Strangeness in set command
Date: Sat, 05 Apr 2008 18:54:00 -0000 [thread overview]
Message-ID: <umyo8rzsk.fsf@gnu.org> (raw)
In-Reply-To: <jey77sp7xr.fsf@sykes.suse.de> (message from Andreas Schwab on Sat, 05 Apr 2008 18:45:04 +0200)
> From: Andreas Schwab <schwab@suse.de>
> Cc: gdb@sources.redhat.com
> Date: Sat, 05 Apr 2008 18:45:04 +0200
>
> > (gdb) set s.st_mode=0x1ff
> > Ambiguous set command "s.st_mode=0x1ff"
> >
> > But this succeeds:
> >
> > (gdb) set (&s)->st_mode=0x1ff
> >
> > How come we are smart enough to support the latter, but not the
> > former?
>
> Because there are several set commands beginning with s. Use set
> variable to avoid the ambiguity.
Thanks.
Does anyone object to improving the error message to mention "set
variable"?
next prev parent reply other threads:[~2008-04-05 17:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 16:49 Eli Zaretskii
2008-04-05 16:56 ` Andreas Schwab
2008-04-05 18:54 ` Eli Zaretskii [this message]
2008-04-07 8:47 ` Daniel Jacobowitz
2008-04-07 18:32 ` Andrew STUBBS
2008-04-07 19:28 ` Michael Snyder
2008-04-07 19:37 ` Eli Zaretskii
2008-04-08 20:38 ` Andrew STUBBS
2008-04-08 20:45 ` Eli Zaretskii
2008-04-09 0:35 ` Doug Evans
2008-04-09 0:44 ` Michael Snyder
2008-04-09 17:24 ` Tom Tromey
2008-04-09 17:36 ` Michael Snyder
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=umyo8rzsk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=schwab@suse.de \
/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