Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Usachev M." <um.lan@mit.ru>
To: gdb@sourceware.org
Subject: gdb && Eclipse && Harvard cpu
Date: Tue, 25 Dec 2007 09:00:00 -0000	[thread overview]
Message-ID: <14493910.post@talk.nabble.com> (raw)


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.
-- 
View this message in context: http://www.nabble.com/gdb----Eclipse----Harvard-cpu-tp14493910p14493910.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.


             reply	other threads:[~2007-12-25  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-25  9:00 Usachev M. [this message]
2007-12-28 18:42 ` Weddington, Eric
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=14493910.post@talk.nabble.com \
    --to=um.lan@mit.ru \
    --cc=gdb@sourceware.org \
    /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