This is the mail archive of the
mailing list for the GDB project.
RE: gdb && Eclipse && Harvard cpu
- From: "Weddington, Eric" <eweddington at cso dot atmel dot com>
- To: "Usachev M." <um dot lan at mit dot ru>, <gdb at sourceware dot org>
- Date: Fri, 28 Dec 2007 11:40:31 -0700
- Subject: RE: gdb && Eclipse && Harvard cpu
- References: <firstname.lastname@example.org>
> -----Original Message-----
> From: Usachev M. [mailto:email@example.com]
> Sent: Tuesday, December 25, 2007 2:00 AM
> To: firstname.lastname@example.org
> Subject: gdb && Eclipse && Harvard cpu
> I use avr-gdb 6.5 && simulavr (latest WinAVR package). When C-program
> contains static variables, gdb works fine (requests locals
> and variables led
> to generation packets like $m800060).
> But if I use stack local variables, command "x my_var" led to
> the packet
> like $m60 (not $m800060).
> And "x *&my_var" works fine - "$m800060").
> I use Eclipse (not command line) where disassemble and
> inspecting locals and
> variables are automatic, so it is important for me to correct
> this problem.
In talking to Joerg Wunsch (co-maintainer of the AVR toolchain, and who
at least uses GDB), he said:
"Sounds like a genuine bug to me. Personally, I never used the "x"
command to print the contents of local variables, but rather the
"p[rint]" command instead."
I know that this may not be much help to you at the moment.
Please fill in a GDB bug report for this for the AVR target, and send me
the bug # so I can track it.