public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jacob at jacob dot remcomp.fr" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/28465] Problems wit long double data in gdb ARM 64 aarch64
Date: Thu, 28 Oct 2021 12:01:46 +0000 [thread overview]
Message-ID: <bug-28465-4717-1nXCsZA2hj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28465-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28465
--- Comment #2 from jacob at jacob dot remcomp.fr ---
> Le 22 oct. 2021 à 17:15, tromey at sourceware dot org <sourceware-bugzilla@sourceware.org> a écrit :
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=28465
>
> 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> ---
> This is pretty surprising.
>
> As a first step, I'd suggest trying a newer version of gdb.
> Perhaps there was some bug that was fixed.
>
> --
> You are receiving this mail because:
> You reported the bug.
OK, downloaded gdb 10.1. Compiled from source. The same bug persists.
Can you please tell me:
Where does (in the source code of gdb) the reading of the inferior’s registers
happen?
Thanks in advance
jacob
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-28 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 18:37 [Bug c++/28465] New: " jacob at jacob dot remcomp.fr
2021-10-22 15:15 ` [Bug c++/28465] " tromey at sourceware dot org
2021-10-28 12:01 ` jacob at jacob dot remcomp.fr [this message]
2021-10-28 18:56 ` simon.marchi at polymtl dot ca
2022-09-01 16:22 ` luis.machado at arm dot com
2022-09-09 8:56 ` luis.machado at arm dot com
2022-09-09 8:56 ` luis.machado at arm dot com
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-28465-4717-1nXCsZA2hj@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).