public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30431] segfault when inspecting remote variable Date: Fri, 02 Jun 2023 15:06:47 +0000 [thread overview] Message-ID: <bug-30431-4717-My4JE87Q0T@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30431-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30431 --- Comment #5 from Tom Tromey <tromey at sourceware dot org> --- Sorry about the delay on this. I think it would be better to understand the problem a little more. The main concern here is that there might be other spots that would be affected, depending on the command you run; but if the problem occurs when reading symbols and is fixed there, then that might fix all instances of the bug. When I run gdb on the ELF you provided, I don't see the crash. But maybe it only occurs when connected to the target. For me gdb thinks the symbol is in: (top-gdb) p *obj_section.the_bfd_section $8 = { name = 0x291928b "__interrupt_vector_4", Maybe one way to reproduce the bug without me needing a working system is a remote log. If you can do something like: $ gdb -nx (gdb) set remotelogfile /tmp/whatever (gdb) target remote ... (gdb) break / continue / whatever to reproduce the bug (gdb) print BCSCTL1 ... then send the log. This can be replayed here without needing anything else. (Though if you have to pass a file when starting gdb, or use "file" or something like that, then the exact files used would also be needed.) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-02 15:06 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-08 21:05 [Bug gdb/30431] New: " marian.buschsieweke at ovgu dot de 2023-05-09 15:01 ` [Bug gdb/30431] " tromey at sourceware dot org 2023-05-09 15:59 ` marian.buschsieweke at ovgu dot de 2023-05-09 16:53 ` marian.buschsieweke at ovgu dot de 2023-06-02 7:19 ` marian.buschsieweke at posteo dot net 2023-06-02 15:06 ` tromey at sourceware dot org [this message] 2023-06-03 18:28 ` marian.buschsieweke at posteo dot net 2023-06-03 18:29 ` marian.buschsieweke at posteo dot net 2023-06-03 20:31 ` tromey at sourceware dot org 2023-06-03 21:33 ` marian.buschsieweke at posteo dot net 2023-06-03 21:35 ` marian.buschsieweke at posteo dot net 2023-06-04 17:25 ` tromey at sourceware dot org 2023-06-04 20:19 ` marian.buschsieweke at posteo dot net 2023-06-20 21:20 ` tromey at sourceware dot org 2023-06-20 21:21 ` tromey at sourceware dot org 2023-07-10 17:19 ` cvs-commit at gcc dot gnu.org 2023-07-10 17:19 ` 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-30431-4717-My4JE87Q0T@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).