public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "bioloidgp at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30238] New: /build/gdb-ktlO15/gdb-9.2/gdb/gdbtypes.c:5126: internal-error: type* copy_type(const type*): Assertion `TYPE_OBJFILE_OWNED (type)' failed.
Date: Thu, 16 Mar 2023 23:37:39 +0000 [thread overview]
Message-ID: <bug-30238-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30238
Bug ID: 30238
Summary: /build/gdb-ktlO15/gdb-9.2/gdb/gdbtypes.c:5126:
internal-error: type* copy_type(const type*):
Assertion `TYPE_OBJFILE_OWNED (type)' failed.
Product: gdb
Version: unknown
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: bioloidgp at gmail dot com
Target Milestone: ---
find 0x0,0x0 ,{long long[0x80000000]}"A"
tested on ubuntu20.04
gef➤ find 0x0,0x0 ,{long long[0x80000000]}"A"
/build/gdb-ktlO15/gdb-9.2/gdb/gdbtypes.c:5126: internal-error: type*
copy_type(const type*): Assertion `TYPE_OBJFILE_OWNED (type)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.
[1] 230 abort (core dumped) gdb ./a.out
tested on ubuntu22.04
pwndbg> find 0x0,0x0 ,{long long[0x80000000]}"A"
/build/gdb-ZgDh0V/gdb-12.1/gdb/gdbtypes.c:5684: internal-error: copy_type:
Assertion `type->is_objfile_owned ()' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
0x5649952c3077 ???
0x564995627a64 ???
0x564995627ca0 ???
0x5649957770e4 ???
0x5649953f32ab ???
0x5649953f6e1b ???
0x5649953f5e77 ???
0x5649953f69c7 ???
0x56499563eb5b ???
0x5649953bf827 ???
0x5649953bfb7d ???
0x5649953de19c ???
0x5649952f8654 ???
0x5649955ee394 ???
0x5649953c69a4 ???
0x5649953c6d43 ???
0x5649953c74c6 ???
0x7f79aa744e0d ???
0x5649953c5a95 ???
0x5649953c7374 ???
0x5649953c568b ???
0x564995777815 ???
0x564995777caa ???
0x56499548336c ???
0x564995485054 ???
0x56499521b15f ???
0x7f79a96bfd8f __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
0x7f79a96bfe3f __libc_start_main_impl
../csu/libc-start.c:392
0x564995220bf4 ???
0xffffffffffffffff ???
---------------------
This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.
[1] 174 IOT instruction ./gdb ./a.out
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-03-16 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 23:37 bioloidgp at gmail dot com [this message]
2023-03-17 2:32 ` [Bug gdb/30238] " simark at simark dot ca
2023-03-17 13:55 ` 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-30238-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: 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).