public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27750] local variables have wrong address and values on sparc64
Date: Sat, 17 Apr 2021 16:51:43 +0000 [thread overview]
Message-ID: <bug-27750-4717-VBd6Xr7Oxf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27750-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27750
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
> Possibly similar to 23220 however on 64-bit recent Debian sid with
I looked at bug #23220, but that one uses stabs, so it's probably
unrelated.
Can you attach your executable? That might provide enough info
to find the problem.
Frequently, though, this kind of thing turns out to be a compiler bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-17 16:51 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 ` tromey at sourceware dot org [this message]
2021-04-17 17:53 ` [Bug gdb/27750] " 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
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-VBd6Xr7Oxf@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).