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 external/8656] Kernel does not support sparse core files
Date: Fri, 22 Mar 2024 12:41:37 +0000 [thread overview]
Message-ID: <bug-8656-4717-Qq7NWsvhyD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-8656-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=8656
Pedro Alves <pedro at palves dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
CC| |pedro at palves dot net
Status|ASSIGNED |RESOLVED
--- Comment #1 from Pedro Alves <pedro at palves dot net> ---
Not sure why this is an open bug. It is just stating a fact AFAICS.
PR 18704 discusses making the testcase detect automatically whether the system
supports sparse cores.
PR 31494 was about GDB's own gcore not producing sparse cores. That is now
fixed, and bigcore.exp runs against gcore too now.
Thus, I'm closing this one.
--
You are receiving this mail because:
You are on the CC list for the bug.
parent reply other threads:[~2024-03-22 12:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-8656-4717@http.sourceware.org/bugzilla/>]
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-8656-4717-Qq7NWsvhyD@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).