This is the mail archive of the gdb@sourceware.org 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: value of local variable stored in register

From: "Jim Blandy" <jimb at red-bean dot com>
To: "Eli Zaretskii" <eliz at gnu dot org>
Cc: kushneeraj at gmail dot com, gdb at sourceware dot org
Date: Tue, 5 Feb 2008 22:26:10 -0800
Subject: Re: value of local variable stored in register
References: <df5e18bd0802032053o7dddab55n6b01a369424e727b@mail.gmail.com> <uwspktqe4.fsf@gnu.org> <8f2776cb0802051142s6ab14bs80f91835da26f4e8@mail.gmail.com> <u3as7ta4b.fsf@gnu.org> <8f2776cb0802051626s7189fd87t12eef4fa45366f7d@mail.gmail.com> <uwspisopi.fsf@gnu.org>

On Feb 5, 2008 8:17 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > (gdb) info address x
> > Symbol "x" is a variable with complex or multiple locations (DWARF2).
>
> That's a bad misfeature.  How about displaying all the possible
> locations, if we cannot say which one is used at the time the command
> is issued?

I agree.  Yes, that's reasonable.  It entails filling in
loclist_describe_location and locexpr_describe_location.

References:
- value of local variable stored in register
  - From: Neeraj kushwaha
- Re: value of local variable stored in register
  - From: Eli Zaretskii
- Re: value of local variable stored in register
  - From: Jim Blandy
- Re: value of local variable stored in register
  - From: Eli Zaretskii
- Re: value of local variable stored in register
  - From: Jim Blandy
- Re: value of local variable stored in register
  - From: Eli Zaretskii

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