This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: gdb && Eclipse && Harvard cpu


> -----Original Message-----
> From: Usachev M. [] 
> Sent: Tuesday, December 25, 2007 2:00 AM
> To:
> 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").
> why?
> 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.

Eric Weddington
Product Manager

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]