Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Internal error for shared library with no .text section
Date: Wed, 15 Apr 2026 21:25:55 +0100	[thread overview]
Message-ID: <cover.1776284661.git.aburgess@redhat.com> (raw)

A Fedora GDB user ran into an issue with a shared library that had no
.text section triggering an internal error from GDB.

Patch #1 is a small refactor.

Patch #2 addresses the issue.

Thanks,
Andrew


---

Andrew Burgess (2):
  gdb: int to bool in struct entry_info
  gdb: don't use .text as default entry point section

 gdb/objfiles.h                                |  8 +-
 gdb/symfile.c                                 | 19 ++--
 .../gdb.base/bad-solib-entry-addr-lib.s       | 33 +++++++
 gdb/testsuite/gdb.base/bad-solib-entry-addr.c | 22 +++++
 .../gdb.base/bad-solib-entry-addr.exp         | 95 +++++++++++++++++++
 5 files changed, 165 insertions(+), 12 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/bad-solib-entry-addr-lib.s
 create mode 100644 gdb/testsuite/gdb.base/bad-solib-entry-addr.c
 create mode 100644 gdb/testsuite/gdb.base/bad-solib-entry-addr.exp


base-commit: cc4600477f621c764011b8e2f5bf1a2ebcffb61a
-- 
2.25.4


             reply	other threads:[~2026-04-15 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 20:25 Andrew Burgess [this message]
2026-04-15 20:25 ` [PATCH 1/2] gdb: int to bool in struct entry_info Andrew Burgess
2026-04-15 20:25 ` [PATCH 2/2] gdb: don't use .text as default entry point section Andrew Burgess

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=cover.1776284661.git.aburgess@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@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