public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "marlenesanchez231+jaime at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27750] local variables have wrong address and values on sparc64
Date: Tue, 28 Sep 2021 01:38:58 +0000 [thread overview]
Message-ID: <bug-27750-4717-VeUlPi77PL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27750-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27750
Chris James <marlenesanchez231+jaime at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marlenesanchez231+jaime@gma
| |il.com
--- Comment #20 from Chris James <marlenesanchez231+jaime at gmail dot com> ---
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./foo_gcc-10...
(gdb) break foo.c:13
Breakpoint 1 at 0x858: file foo.c, line 13.
(gdb) run
https://nymphs-in-gardens.tumblr.com/
https://sophiexbx.tumblr.com/
https://benderindeniz.tumblr.com/
https://he1943.tumblr.com/
https://jamischwin.tumblr.com/
Starting program: /home/dclarke/foo_gcc-10
a = 1
&a = 0x7fefffff4fc
https://babyblue1984.tumblr.com/
https://lilysinthefall.tumblr.com/
https://never-gonna-be-alone-sz.tumblr.com/
https://bipolvrsunshine.tumblr.com/
https://youareatypo.tumblr.com/
Breakpoint 1, main (argc=1, argv=0x7fefffff8a8) at foo.c:13
13 return EXIT_SUCCESS;
(gdb) print &a
$1 = (int *) 0x7fefffff4fc
(gdb) print a
$2 = 1
(gdb) info frame
Stack level 0, frame at 0x7fefffff500:
pc = 0x10000000858 in main (foo.c:13); saved pc = 0xfffff8010014e804
source language c.
Arglist at 0x7fefffff500, args: argc=1, argv=0x7fefffff8a8
Locals at 0x7fefffff500, Previous frame's sp in fp
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-28 1:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 16:15 [Bug gdb/27750] New: " dclarke at blastwave dot org
2021-04-17 16:51 ` [Bug gdb/27750] " tromey at sourceware dot org
2021-04-17 17:53 ` dclarke at blastwave dot org
2021-04-17 17:55 ` dclarke at blastwave dot org
2021-04-17 17:56 ` dclarke at blastwave dot org
2021-04-17 20:32 ` tromey at sourceware dot org
2021-04-17 22:55 ` dclarke at blastwave dot org
2021-04-18 1:21 ` simark at simark dot ca
2021-04-18 1:57 ` tromey at sourceware dot org
2021-04-19 0:51 ` simark at simark dot ca
2021-04-19 10:44 ` dclarke at blastwave dot org
2021-04-19 12:31 ` glaubitz at physik dot fu-berlin.de
2021-04-19 13:29 ` tromey at sourceware dot org
2021-06-27 17:54 ` ahmedsayeed1982 at yahoo dot com
2021-08-10 12:45 ` ucelsanicin at yahoo dot com
2021-08-23 6:05 ` marlenesanchez231+gaby at gmail dot com
2021-08-23 6:54 ` mark at klomp dot org
2021-09-02 11:06 ` donipah907 at mtlcz dot com
2021-09-06 9:09 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:39 ` mehmetgelisin at aol dot com
2021-09-14 12:54 ` jarilittlenen at yahoo dot com
2021-09-22 10:19 ` diheto5497 at secbuf dot com
2021-09-28 1:38 ` marlenesanchez231+jaime at gmail dot com [this message]
2021-10-09 11:00 ` gulsenenginar at aol dot com
2021-10-10 16:11 ` oficaj3 at gmail dot com
2021-10-19 7:13 ` progonsaytu at gmail dot com
2021-10-24 10:01 ` glassmtech at ukr dot net
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=bug-27750-4717-VeUlPi77PL@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).