This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Static variables incorrect address
- From: "Salman Khilji" <salmankhilji at hotmail dot com>
- To: gdb at sources dot redhat dot com
- Date: Fri, 22 Mar 2002 01:11:21 +0000
- Subject: Re: Static variables incorrect address
- Bcc:
I would tend to agree with Mike. I have used this feature with lots of
different cases. It works very nicely with both C and C++. plus, you dont'
even have to issue the run command. You can lookup the address right after
the startup.
There was once a problem with static member variables like these inside C++
namepsaces. But that was fixed in 5.1
Salman
>From: Michael Snyder <msnyder@redhat.com>
>To: Kiranmaye Gannabathula <kiranmaye.gannabathula@powervr.com>
>CC: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
>Subject: Re: Static variables incorrect address
>Date: Thu, 21 Mar 2002 16:12:53 -0800
>
>Kiranmaye Gannabathula wrote:
> >
> > Hello,
> > I have a problem with the global static variables in gdb.
> >
> > For a C program as below
> >
> > static int Data = 9;
> >
> > int Func1(void)
> > {
> > return Data;
> > }
> >
> > if i compile this with debug info and run it under gdb, when i
>breakpoint on
> > the variable Data and try to print its value i get some value and
> > if i look at the address
> > p /x Data
> > i get some invalid address.
>
>I believe you want to say "p /x &Data".
>Otherwise you will be looking at memory at an address
>determined by the value of the variable "Data".
_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail.
http://www.hotmail.com