From: "Salman Khilji" <salmankhilji@hotmail.com>
To: gdb@sources.redhat.com
Subject: Re: Static variables incorrect address
Date: Thu, 21 Mar 2002 17:11:00 -0000 [thread overview]
Message-ID: <F7kNUTvl7PDqqgNjWOi000025fd@hotmail.com> (raw)
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
next reply other threads:[~2002-03-22 1:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 17:11 Salman Khilji [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-21 9:18 Kiranmaye Gannabathula
2002-03-21 11:34 ` Eli Zaretskii
2002-03-21 16:23 ` Michael Snyder
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=F7kNUTvl7PDqqgNjWOi000025fd@hotmail.com \
--to=salmankhilji@hotmail.com \
--cc=gdb@sources.redhat.com \
/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