From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6926 invoked by alias); 28 Dec 2007 18:42:40 -0000 Received: (qmail 6917 invoked by uid 22791); 28 Dec 2007 18:42:39 -0000 X-Spam-Check-By: sourceware.org Received: from newsmtp5.atmel.com (HELO sjogate2.atmel.com) (204.2.163.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 28 Dec 2007 18:42:35 +0000 Received: from csomb01.corp.atmel.com ([10.95.30.150]) by sjogate2.atmel.com (8.13.6/8.13.6) with ESMTP id lBSIeiQm003701; Fri, 28 Dec 2007 10:40:44 -0800 (PST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: gdb && Eclipse && Harvard cpu Date: Fri, 28 Dec 2007 18:42:00 -0000 Message-ID: <258DDD1F44B6ED4AAFD4370847CF58D5630EF8@csomb01.corp.atmel.com> In-Reply-To: <14493910.post@talk.nabble.com> References: <14493910.post@talk.nabble.com> From: "Weddington, Eric" To: "Usachev M." , Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-12/txt/msg00189.txt.bz2 =20 > -----Original Message----- > From: Usachev M. [mailto:um.lan@mit.ru]=20 > Sent: Tuesday, December 25, 2007 2:00 AM > To: gdb@sourceware.org > Subject: gdb && Eclipse && Harvard cpu >=20 >=20 > I use avr-gdb 6.5 && simulavr (latest WinAVR package). When C-program > contains static variables, gdb works fine (requests locals=20 > and variables led > to generation packets like $m800060). > But if I use stack local variables, command "x my_var" led to=20 > the packet > like $m60 (not $m800060).=20 > And "x *&my_var" works fine - "$m800060"). > why? >=20 > I use Eclipse (not command line) where disassemble and=20 > inspecting locals and > variables are automatic, so it is important for me to correct=20 > 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