Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] gdb/coffread: simplify stab section detection
Date: Fri, 9 Jan 2026 14:36:39 -0500	[thread overview]
Message-ID: <94f7f8f2-8e79-414e-98e6-8bd7e8ce6d2f@simark.ca> (raw)
In-Reply-To: <87ikdalh4a.fsf@tromey.com>

On 1/9/26 2:29 PM, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
> 
> Simon> We look for stab sections for the sole purpose of emitting a warning if
> Simon> we see one.  Simplify this by using a boolean to indicate if we saw a
> Simon> stab section or not.  Simplify the search to just look for sections
> Simon> starting with ".stab", it should be enough for this purpose.
> 
> Simon> Also, remove the make_scoped_restore that would overwrite the stab
> Simon> section vector, I'm not sure why it's there.  It seems to me like it
> Simon> would cause the warning to never be shown.
> 
> Simon> @@ -47,7 +47,8 @@ struct coff_symfile_info
> Simon>      file_ptr min_lineno_offset = 0;	/* Where in file lowest line#s are.  */
> Simon>      file_ptr max_lineno_offset = 0;	/* 1+last byte of line#s in file.  */
>  
> Simon> -    std::vector<asection *> *stabsects;	/* .stab sections.  */
> Simon> +    /* True if the symfile contains one section that starts with ".stab".  */
> Simon> +    bool found_stab_section = false;
> 
> There's not really a reason to keep this in coff_symfile_info.  That
> said it hardly hurts and this is definitely an improvement regardless.
> 
> Simon>    if (!(objfile->flags & OBJF_READNEVER))
> Simon>      bfd_map_over_sections (abfd, coff_locate_sections, (void *) info);
> 
> ... I'd imagine it's a workaround for mapping over sections like this
> rather than just using foreach.  The latter makes it easier to do random
> checks.
> 
> Approved-By: Tom Tromey <tom@tromey.com>
> 
> Tom

You're right, I'll simplify this further.  I have pushed the first two
patches.

Simon

  reply	other threads:[~2026-01-09 19:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 19:14 [PATCH 1/3] gdb/coffread: remove unnecessary forward declarations Simon Marchi
2026-01-09 19:14 ` [PATCH 2/3] gdb/coffread: remove unused fields of coff_symfile_info Simon Marchi
2026-01-09 19:24   ` Tom Tromey
2026-01-09 19:14 ` [PATCH 3/3] gdb/coffread: simplify stab section detection Simon Marchi
2026-01-09 19:29   ` Tom Tromey
2026-01-09 19:36     ` Simon Marchi [this message]
2026-01-09 19:41   ` [PATCH v2] " Simon Marchi
2026-01-09 20:49     ` Tom Tromey
2026-01-09 21:38       ` Simon Marchi
2026-01-09 19:24 ` [PATCH 1/3] gdb/coffread: remove unnecessary forward declarations Tom Tromey

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=94f7f8f2-8e79-414e-98e6-8bd7e8ce6d2f@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.com \
    --cc=tom@tromey.com \
    /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