public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/30705] [gdb] UNRESOLVED: gdb.base/all-architectures-2.exp: tests: osabi=AIX: arch=bpf: endian=auto: disassemble 0x100,+4 (segfault) Date: Mon, 31 Jul 2023 11:03:44 +0000 [thread overview] Message-ID: <bug-30705-4717-nyWplSQpWm@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30705-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30705 --- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> --- Also, I'm seeming in gdb.gdb/unittest.exp: ... Running selftest buffered_insn_length::bpf.^M ^M ^M Fatal signal: Segmentation fault^M ... Reproducer: ... $ gdb -q -batch -ex "maint selftest buffered_insn_length::bpf" ... In this case, we're segfaulting here because abfd is nullptr: ... Thread 1 "gdb" received signal SIGSEGV, Segmentation fault. print_insn_bpf (pc=0, info=0x7fffffffd398) at /data/vries/gdb/src/opcodes/bpf-dis.c:153 153 Elf_Internal_Ehdr *header = elf_elfheader (abfd); ... which gets it's value in the same line as mentioned in comment 3: ... 152 struct bfd *abfd = info->section->owner; ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-31 11:03 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-31 9:59 [Bug gdb/30705] New: " vries at gcc dot gnu.org 2023-07-31 10:01 ` [Bug gdb/30705] " vries at gcc dot gnu.org 2023-07-31 10:07 ` vries at gcc dot gnu.org 2023-07-31 10:09 ` vries at gcc dot gnu.org 2023-07-31 10:14 ` [Bug tdep/30705] " vries at gcc dot gnu.org 2023-07-31 10:45 ` jose.marchesi at oracle dot com 2023-07-31 11:03 ` vries at gcc dot gnu.org [this message] 2023-07-31 11:16 ` vries at gcc dot gnu.org 2023-07-31 13:03 ` mark at klomp dot org 2023-07-31 13:46 ` cvs-commit at gcc dot gnu.org 2023-07-31 14:15 ` vries at gcc dot gnu.org 2023-07-31 21:04 ` vries at gcc dot gnu.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-30705-4717-nyWplSQpWm@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).