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/26863] GDB crash when opening PowerPC core on x86-64 machine Date: Tue, 10 Nov 2020 21:06:41 +0000 [thread overview] Message-ID: <bug-26863-4717-prBNWl3sk0@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26863-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26863 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #3 from Tom Tromey <tromey at sourceware dot org> --- It's difficult to know if this papers over anything. The old code probably just worked by mistake: - struct target_section *p; - - for (p = solib->sections; p < solib->sections_end; p++) - if (p->addr <= address && address < p->endaddr) The loop will presumably not run because both pointers are null. Tom de Vries checked in the null check a while back. commit 76547ab31b16b521e29892cab5a29b60b52291a5 Author: Tom de Vries <tdevries@suse.de> Date: Wed Oct 14 12:24:42 2020 +0200 [gdb] Fix segfault in solib_contains_address_p So maybe this is just a dup of PR 26733. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-10 21:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-10 16:48 [Bug gdb/26863] New: " simark at simark dot ca 2020-11-10 17:36 ` [Bug gdb/26863] " simark at simark dot ca 2020-11-10 17:47 ` simark at simark dot ca 2020-11-10 21:06 ` tromey at sourceware dot org [this message] 2020-11-10 21:12 ` simark at simark dot ca
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-26863-4717-prBNWl3sk0@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).