Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 3/3] gdb: extend the [[N]]::foo syntax for files
Date: Thu, 10 Jul 2025 11:47:05 -0300	[thread overview]
Message-ID: <8ed10634-662e-45fa-ae67-959b60aedd93@redhat.com> (raw)
In-Reply-To: <20250709190226.41d1be21@f41-zbm-amd>

On 7/9/25 11:02 PM, Kevin Buettner wrote:
> Hi Gwen,
>
> On Thu, 19 Jun 2025 15:05:40 -0300
> Guinevere Larsen <guinevere@redhat.com> wrote:
>
>> diff --git a/gdb/parse.c b/gdb/parse.c
>> index 64653c8ae6e..6edd9058dcb 100644
>> --- a/gdb/parse.c
>> +++ b/gdb/parse.c
>> @@ -421,7 +421,8 @@ parse_exp_in_context (const char **stringptr,
>> CORE_ADDR pc,
>>     parser_state ps (lang, get_current_arch (), expression_context_block,
>>   		   expression_context_pc, flags, *stringptr,
>> -		   completer != nullptr, tracker);
>> +		   completer != nullptr, tracker,
>> +		   current_program_space->solib_ops ());
>>   
>>     scoped_restore_current_language lang_saver (lang->la_language);
>>   
> I'm seeing a build error related to the bit above:
>
> /mesquite2/sourceware-git/worktree-review/gdb/parse.c: In function
> ‘expression_up parse_exp_in_context(const char**, CORE_ADDR, const block*,
> parser_flags, innermost_block_tracker*,
> std::unique_ptr<expr_completion_base>*)’:
> /mesquite2/sourceware-git/worktree-review/gdb/parse.c:425:53: error:
> invalid conversion from ‘const solib_ops*’ to ‘solib_ops*’ [-fpermissive]
> 425 |                    current_program_space->solib_ops ()); |
>          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~ |
>                        | |
>    const solib_ops* In file included from
> /mesquite2/sourceware-git/worktree-review/gdb/parse.c:41:
> /mesquite2/sourceware-git/worktree-review/gdb/parser-defs.h:152:28: note:
> initializing argument 9 of ‘parser_state::parser_state(const
> language_defn*, gdbarch*, const block*, CORE_ADDR, parser_flags, const
> char*, bool, innermost_block_tracker*, solib_ops*)’ 152 |
> solib_ops *ops) |                 ~~~~~~~~~~~^~~
>
> Kevin
>
Ah, thanks for reporting this, I must have not redone a build when I 
sent this (sorry, it was pre-vacation rush).

This is trivially solved by making all solib_ops pointers in 
parser_state const, I fixed it locally

-- 
Cheers,
Guinevere Larsen
She/Her/Hers


  reply	other threads:[~2025-07-10 14:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 18:05 [PATCH v3 0/3] Introduce syntax for linker-namespace specific symbols Guinevere Larsen
2025-06-19 18:05 ` [PATCH v3 1/3] gdb: make lookup_minimal_symbol_linkage work with linker namespaces Guinevere Larsen
2025-06-19 18:05 ` [PATCH v3 2/3] gdb: Make the parser recognize the [[N]] syntax for variables Guinevere Larsen
2025-06-20  6:57   ` Eli Zaretskii
2025-07-07 19:18     ` Guinevere Larsen
2025-06-19 18:05 ` [PATCH v3 3/3] gdb: extend the [[N]]::foo syntax for files Guinevere Larsen
2025-07-10  2:02   ` Kevin Buettner
2025-07-10 14:47     ` Guinevere Larsen [this message]
2025-07-10  2:27   ` Kevin Buettner
2025-07-10 15:07     ` Guinevere Larsen
2025-07-10 21:56       ` Kevin Buettner
2025-07-07 19:01 ` [PING][PATCH v3 0/3] Introduce syntax for linker-namespace specific symbols Guinevere Larsen

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=8ed10634-662e-45fa-ae67-959b60aedd93@redhat.com \
    --to=guinevere@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.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