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 gdb/29295] [gdb] out of bounds access in objfile::section_offset
Date: Mon, 11 Jul 2022 16:19:07 +0000	[thread overview]
Message-ID: <bug-29295-4717-kRiLHC5Fxm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29295-4717@http.sourceware.org/bugzilla/>

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

--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #7)
> Created attachment 14203 [details]
> WIP patch
> 

Well, it passes testing.

It just that it's hard to make sure that the patch is complete.

I tried a bit with making gdb_bfd_section_index return a
gdb_bfd_section_index_t which is defined as:
...
   enum class gdb_bfd_section_index_t : int {};
...
such that we always known whether we have a bfd section or a gdb_bfd section
index, but that looks like a lot of changes.

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

  parent reply	other threads:[~2022-07-11 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28  6:45 [Bug gdb/29295] New: " vries at gcc dot gnu.org
2022-06-28  7:16 ` [Bug gdb/29295] " vries at gcc dot gnu.org
2022-06-28 11:59 ` vries at gcc dot gnu.org
2022-06-29 13:14 ` vries at gcc dot gnu.org
2022-06-30 11:12 ` vries at gcc dot gnu.org
2022-06-30 11:18 ` vries at gcc dot gnu.org
2022-06-30 11:20 ` vries at gcc dot gnu.org
2022-07-11 14:55 ` vries at gcc dot gnu.org
2022-07-11 16:19 ` vries at gcc dot gnu.org [this message]
2022-07-11 22:24 ` vries at gcc dot gnu.org
2022-07-12  8:01 ` vries at gcc dot gnu.org
2022-07-12 14:17 ` 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-29295-4717-kRiLHC5Fxm@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).