This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Strangeness in set command
- From: Andreas Schwab <schwab at suse dot de>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb at sources dot redhat dot com
- Date: Sat, 05 Apr 2008 18:45:04 +0200
- Subject: Re: Strangeness in set command
- References: <uod8os2n1.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> Assuming that `s' is a variable of type `struct stat', this command
> fails:
>
> (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.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."