public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at palves dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30525] gdb cannot read shared libraries on SPARC64
Date: Wed, 07 Jun 2023 22:12:14 +0000 [thread overview]
Message-ID: <bug-30525-4717-4tQxjun4Mn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30525-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30525
Pedro Alves <pedro at palves dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #14925|[PATCH] Avoid |[PATCH] Avoid
description|pread64/pwrite64 for high |pread64/pwrite64 for high
|memory addresses |memory addresses (v3)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-07 22:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 19:19 [Bug gdb/30525] New: " mattst88 at gmail dot com
2023-06-06 19:19 ` [Bug gdb/30525] " mattst88 at gmail dot com
2023-06-06 22:27 ` mattst88 at gmail dot com
2023-06-07 8:36 ` sam at gentoo dot org
2023-06-07 8:37 ` sam at gentoo dot org
2023-06-07 9:05 ` pedro at palves dot net
2023-06-07 10:19 ` pedro at palves dot net
2023-06-07 10:44 ` pedro at palves dot net
2023-06-07 14:43 ` mattst88 at gmail dot com
2023-06-07 15:18 ` mattst88 at gmail dot com
2023-06-07 15:33 ` mattst88 at gmail dot com
2023-06-07 22:11 ` pedro at palves dot net
2023-06-07 22:12 ` pedro at palves dot net [this message]
2023-06-07 23:57 ` mattst88 at gmail dot com
2023-06-14 23:42 ` mattst88 at gmail dot com
2023-06-15 10:39 ` pedro at palves dot net
2023-07-05 13:43 ` pedro at palves dot net
2023-07-06 16:58 ` cvs-commit at gcc dot gnu.org
2023-07-06 20:55 ` sam at gentoo dot org
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-30525-4717-4tQxjun4Mn@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).