Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Weddington, Eric" <eweddington@cso.atmel.com>
To: "Usachev M." <um.lan@mit.ru>, <gdb@sourceware.org>
Subject: RE: gdb && Eclipse && Harvard cpu
Date: Fri, 28 Dec 2007 18:42:00 -0000	[thread overview]
Message-ID: <258DDD1F44B6ED4AAFD4370847CF58D5630EF8@csomb01.corp.atmel.com> (raw)
In-Reply-To: <14493910.post@talk.nabble.com>

 

> -----Original Message-----
> From: Usachev M. [mailto:um.lan@mit.ru] 
> Sent: Tuesday, December 25, 2007 2:00 AM
> To: gdb@sourceware.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").
> 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.

Thanks,
Eric Weddington
Product Manager
Atmel


  reply	other threads:[~2007-12-28 18:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-25  9:00 Usachev M.
2007-12-28 18:42 ` Weddington, Eric [this message]
2007-12-29  7:06   ` Usachev M.

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=258DDD1F44B6ED4AAFD4370847CF58D5630EF8@csomb01.corp.atmel.com \
    --to=eweddington@cso.atmel.com \
    --cc=gdb@sourceware.org \
    --cc=um.lan@mit.ru \
    /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