public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "sudoaptgetmypy at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/26118] New: dump srec memory foo 0x0 0xffffffffff raises internal error on Chrome OS Date: Mon, 15 Jun 2020 20:59:30 +0000 [thread overview] Message-ID: <bug-26118-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26118 Bug ID: 26118 Summary: dump srec memory foo 0x0 0xffffffffff raises internal error on Chrome OS Product: gdb Version: 8.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: sudoaptgetmypy at gmail dot com Target Milestone: --- I was debugging some code once. I did: ``` $ g++ -o main main.cpp $ ./main $ gdb main GNU gdb (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from main...(no debugging symbols found)...done. (gdb) dump srec memory foo 0x0 0xffffffffff /build/gdb-kAlH5B/gdb-8.1/gdb/utils.c:778: internal-error: virtual memory exhausted: can't allocate 1099511627775 bytes. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) n This is a bug, please report it. For instructions, see: <http://www.gnu.org/software/gdb/bugs/>. /build/gdb-kAlH5B/gdb-8.1/gdb/utils.c:778: internal-error: virtual memory exhausted: can't allocate 1099511627775 bytes. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) ``` -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-06-15 20:59 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-15 20:59 sudoaptgetmypy at gmail dot com [this message] 2024-01-03 15:01 ` [Bug c++/26118] " ssbssa 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-26118-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).