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/31494] New: gcore should generate sparse cores Date: Fri, 15 Mar 2024 15:34:07 +0000 [thread overview] Message-ID: <bug-31494-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31494 Bug ID: 31494 Summary: gcore should generate sparse cores Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: pedro at palves dot net Target Milestone: --- As can be seen with the gdb.base/bigcore.exp program: $ gdb -q --batch ./testsuite/outputs/gdb.base/bigcore/bigcore -ex "run" -ex "gcore /tmp/core.gdb" (...) Dump core .... Program received signal SIGSEGV, Segmentation fault. main () at gdb.base/bigcore.c:270 270 *(volatile char*)0 = 0; warning: Memory read failed for corefile section, 4096 bytes at 0xffffffffff600000. Saved corefile /tmp/core.gdb $ du --hu /tmp/core.gdb 16G /tmp/core.gdb $ du --hu --apparent-size /tmp/core.gdb 16G /tmp/core.gdb ... GDB isn't generating sparse core files. It would good if it did. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-03-15 15:34 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-15 15:34 pedro at palves dot net [this message] 2024-03-15 15:34 ` [Bug gdb/31494] " pedro at palves dot net 2024-03-15 15:35 ` [Bug corefiles/31494] " pedro at palves dot net 2024-03-15 18:32 ` pedro at palves dot net 2024-03-22 12:31 ` cvs-commit at gcc dot gnu.org 2024-03-22 12:34 ` pedro at palves dot net 2024-03-22 15:33 ` tromey at sourceware 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-31494-4717@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: linkBe 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).