Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: info locals gives error
Date: Fri, 31 Mar 2006 13:53:00 -0000	[thread overview]
Message-ID: <uzmj79gcf.fsf@gnu.org> (raw)
In-Reply-To: <17452.52811.89546.605084@farnswood.snap.net.nz> (message from 	Nick Roberts on Fri, 31 Mar 2006 18:38:03 +1200)

> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Fri, 31 Mar 2006 18:38:03 +1200
> 
> I've just upgraded to Fedora Core 5 (kernel 2.6.15-1.2054_FC5) and with the
> program below I get errors which didn't occur before (Fedora Core 3).  This
> error might relate to Vladimir Prus's earlier report
> (http://sources.redhat.com/ml/gdb-patches/2006-03/msg00225.html) and
> value_print.
> 
> 
> /* -*- compile-command: "cc -g -o simple simple.c"; -*- */
> 
> main(int argc, char **argv) {
>   int i;
>   i = 1;
> }
> [...]
>   (gdb) b main
>   Breakpoint 1 at 0x8048354: file simple.c, line 3.
>   (gdb) r
>   Starting program: /home/nickrob/simple
>   Reading symbols from shared object read from target memory...done.
>   Loaded system supplied DSO at 0x80e000
>   
>   Breakpoint 1, main () at simple.c:3
>   3       main(int argc, char **argv) {
>   (gdb) info locals
>   argc = Cannot access memory at address 0x0

I cannot reproduce this with GDB 6.4 and GCC versions 3.3.5 and 4.0.0
on a Debian box.  I also tried GCC 3.4.2 and GDB 6.3 on a Windows box.
What I get in all of those cases is some arbitrary garbage, not
"cannot access".


  reply	other threads:[~2006-03-31  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31  6:57 Nick Roberts
2006-03-31 13:53 ` Eli Zaretskii [this message]
2006-04-02  6:59   ` Nick Roberts

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=uzmj79gcf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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