I think you should use 'set var b=20'
ramadewa wrote:
gdb seems to think b represents a command line option (backtrace or
breakpoint). This tends to happen when trying to set 1-character variables.
If you rename your variable to boy, it should work fine. Or, you can use
print b=50 to set (and view) b.
tej wrote:
hi friends ,
i am running simulavr in the background and then using gdb as the
debugger for
my program for the device at90s8515. during debugging process when I type
set b = 50 at the (gdb) prompt , it gves the following error :
Ambiguous set command "b=50" ; backtrace , breakpoint
(gdb) print b is working fine .
what can be the reason for this error.( I am using gdb 6.4).
tej
--
View this message in context:
http://www.nabble.com/ambiguous-set-command-t1379194.html#a4019953
Sent from the Gnu - gdb - General forum at Nabble.com.
_______________________________________________
Gdb mailing list
Gdb@gnu.org
http://lists.gnu.org/mailman/listinfo/gdb
_______________________________________________
Gdb mailing list
Gdb@gnu.org
http://lists.gnu.org/mailman/listinfo/gdb
