Re: [PATCH] gdb: ensure bp_location::section is set correct to avoid an assert

[Andrew Burgess <aburgess@redhat.com>]

Simon Marchi <simark@simark.ca> writes:

> On 9/25/25 1:56 PM, Andrew Burgess wrote:
>> Part of the reason I'd push for a wider fix is that there are lots
>> different linespec formats, and I don't think they all pass through
>> minsym_found (or maybe they do?).
>
> It's certainly possble to create SALs without going through
> minsym_found.
>
>> If they don't then it feels like you should be able to adjust your
>> original test such that minsym_found isn't called, and you'll have the
>> same incorrect gdbarch problem.  So then you'll have to add a
>> find_pc_section in _another_ place....
>
> If the test was compiled with DWARF info, the SAL would be created from
> a full (DWARF) symbol, and we'd go through another path that would cause
> the section field to be set.  I think find_function_start_sal ->
> find_function_start_sal_1.  In this case the section would be known from
> the struct symbol.
>
> I went a bit down the overlay rabbit hole, and I think that your change
> might have broken that (but... I don't know how to test that).  Here's
> the summary of my findings (I'm perhaps completely wrong).
>
> Two ELF sections overlay each other if they have the same VMA but
> different LMA.
>
>  - LMA is the address where the code is permanently stored (e.g. large
>    flash memory, non-executable).  Unique for each section.
>  - VMA is the address where the code gets copied when executed (e.g.
>    small RAM, executable).
>
> An overlay manager in the program takes care of copying the right
> section from its LMA to its VMA before executing it.
>
> My understanding is that the ELF symbols for the various functions in
> these overlaying region have VMA region of memory.  So, you would have
> overlapping ELF symbols, but you can know which ELF symbol is part of
> which section, because ELF symbols have a "section index" property.  We
> record that in minimal_symbol::m_section.
>
> Before your patch, when seting a breakpoint by minimal symbol in an
> overlay situation, this:
>
>   sal.section = msymbol->obj_section (objfile);
>
> would return the right section based on the minimal symbol you
> specified.  I guess this is important later.  To know if it should
> insert the breakpoint location, GDB must decide if the breakpoint
> location is in the section currently mapped at the VMA or not.  For
> that, it needs to know in which section you intended to put the
> breakpoint.  However, the new line:
>
>   sal.section = find_pc_overlay (sal.pc);
>
> would return one of the multiple sections in which sal.pc (a VMA)
> appears, possibly the wrong one.  This would mess up the "should we
> insert this location" logic later.

That sounds reasonable enough.  But the original code was still wrong I
think.

I don't have time right now to reexamine the code I'm afraid, so I'm
going from memory a bit here.

But in the ifunc case, I think MSYMBOL is the symbol from the resolver,
not the actual function where the breakpoint is being placed.

Maybe the answer is as simple as moving the .section assignment into the
earlier if block, something like:

  if (is_function && want_start_sal)
    {
      sal = find_function_start_sal (func_addr, NULL, self->funfirstline);

      /* This breakpoint is for the ifunc case, FUNC_ADDR is can be
         anywhere, in a completely different section to MSYMBOL, or even
         in a different objfile!

         TODO: I haven't checked, maybe find_function_start_sal already
         fills this stuff in for us?  Or maybe it could be made too?
         For now I'm assuming all we have is an address, but this needs
         checking.  */
      sal.section = find_pc_overlay (func_addr);
      if (sal.section == nullptr)
        sal.section = find_pc_section (func_addr);
    }
  else
    {
      sal.objfile = objfile;
      sal.msymbol = msymbol;
      /* Store func_addr, not the minsym's address in case this was an
	 ifunc that hasn't been resolved yet.  */
      if (is_function)
	sal.pc = func_addr;
      else
	sal.pc = msymbol->value_address (objfile);
      sal.pspace = current_program_space;

      /* We can assign the section based on MSYMBOL here because the
         breakpoint is actually being placed at (or near) MSYMBOL.  */
      sal.section = msymbol->obj_section (objfile);
    }

Now we retain the use of MSYMBOL where we can, which addresses the valid
issues you identify above.

But we no longer use MSYMBOL when it's the wrong thing to do, which
addresses the problem I was trying to fix.

Does this look like a valid path forward maybe?

FYI: I'm off work for a couple of days now, but will catch up when I
return.  There was a test with my original change, so as long as that's
still passing I'm happy with whatever you think best.

Thanks,
Andrew