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 remote/28360] segfault in bfd_get_elf_phdr_upper_bound
Date: Tue, 21 Sep 2021 11:31:07 +0000	[thread overview]
Message-ID: <bug-28360-4717-mj08GkVkTi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28360-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28360

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
With this:
...
diff --git a/gdb/linux-tdep.c b/gdb/linux-tdep.c
index ae2f7c14f6d..d7eaa75a34a 100644
--- a/gdb/linux-tdep.c
+++ b/gdb/linux-tdep.c
@@ -2327,7 +2327,7 @@ linux_vsyscall_range_raw (struct gdbarch *gdbarch, struct
mem_ra
nge *range)
   /* It doesn't make sense to access the host's /proc when debugging a
      core file.  Instead, look for the PT_LOAD segment that matches
      the vDSO.  */
-  if (!target_has_execution ())
+  if (!target_has_execution () && core_bfd != nullptr)
     {
       long phdrs_size;
       int num_phdrs, i;
...
we have instead:
...
(gdb) set sysroot remote:^M
warning: "remote:" is deprecated, use "target:" instead.^M
warning: sysroot set to "target:".^M
warning: unable to open /proc file '/proc/0/task/0/maps'^M
(gdb) PASS: gdb.server/server-exec-info.exp: set sysroot remote:
info files^M
(gdb) FAIL: gdb.server/server-exec-info.exp: info files
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2021-09-21 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21 11:18 [Bug remote/28360] New: " vries at gcc dot gnu.org
2021-09-21 11:31 ` vries at gcc dot gnu.org [this message]
2021-09-21 12:34 ` [Bug remote/28360] " 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-28360-4717-mj08GkVkTi@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).