public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jarilittlenen at yahoo 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, 14 Sep 2021 12:54:26 +0000	[thread overview]
Message-ID: <bug-27750-4717-eqRwgLwhY4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27750-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27750

Jari Littlenen <jarilittlenen at yahoo dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jarilittlenen at yahoo dot com

--- Comment #18 from Jari Littlenen <jarilittlenen at yahoo dot com> ---
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./foo_gcc-10...
(gdb) break foo.c:13 http://codefreewifigratuit.xyz/
Breakpoint 1 at 0x858: file foo.c, line 13.
(gdb) run
Starting program: /home/dclarke/foo_gcc-10 
a = 1
&a = 0x7fefffff5fc

Breakpoint 1, main (argc=0, argv=0x0) at foo.c:13
13    https://fraisiachris.fr/      return EXIT_SUCCESS;
(gdb) print a
$1 = 0
(gdb) print &a
$2 = (int *) 0x7feffd7727b
(gdb) info frame
Stack level 0, frame at 0x7feffd7727f:
 pc = 0x10000000858 in main (foo.c:13); saved pc = 0x7feffd76a88
 source language c.
 Arglist at 0x7feffd76a80, args: argc=0, argv=0x0
 Locals at 0x7feffd76a80, Previous frame's sp in fp
 Saved registers: http://www.canalisationengorgee.fr/
  l0 at 0x7feffd7727f, l1 at 0x7feffd77287, l2 at 0x7feffd7728f, l3 at
0x7feffd77297, l4 at 0x7feffd7729f, l5 at 0x7feffd772a7,
  l6 at 0x7feffd772af, l7 at 0x7feffd772b7, i0 at 0x7feffd772bf, i1 at
0x7feffd772c7, i2 at 0x7feffd772cf, i3 at 0x7feffd772d7,
  i4 at 0x7feffd772df, i5 at 0x7feffd772e7, fp at 0x7feffd772ef, i7 at
0x7feffd772f7
(gdb) cont
Continuing.
[Inferior 1 (process 104253) exited normally]
(gdb) quit
mimas$ 
https://www.vincentlevi.com/
Not sure how this compares to the gdb 8.3.1 : 

mimas$ 
mimas$ TERM=dumb LC_ALL=C /usr/local/bin/gdb ./foo_gcc-10

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-09-14 12:54 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 [this message]
2021-09-22 10:19 ` diheto5497 at secbuf dot com
2021-09-28  1:38 ` marlenesanchez231+jaime at gmail dot com
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-eqRwgLwhY4@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).