Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jan Vraný" <Jan.Vrany@labware.com>
To: "tom@tromey.com" <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 13/13] gdb: update message in symbol_file_add_with_addrs after changes in readnow_functions
Date: Tue, 2 Dec 2025 18:48:26 +0000	[thread overview]
Message-ID: <576dde3ff5c99574ff024b6590c255ea356b1a1b.camel@labware.com> (raw)
In-Reply-To: <87ikeo94hb.fsf@tromey.com>

On Tue, 2025-12-02 at 10:29 -0700, Tom Tromey wrote:
> > > > > > "Jan" == Jan Vrany <jan.vrany@labware.com> writes:
> 
> Jan> When loading a file with -readnow, GDB prints message like:
> Jan>     Reading symbols from some_program...
> Jan>     Expanding full symbols from some_program...
> 
> Jan> I assume the reason for the second message ("Expanding ...") is to let
> Jan> the user know what's happening as symbol expansion may take time.
> 
> Yeah.
> 
> I wonder if instead of rewriting expand_all_symtabs in this series, you
> could leave most of that patch in place but still have
> readnow_functions::expand_all_symtabs actually do the work.

Sure. 

> 
> Then when/if readnow_functions is moved out of the DWARF reader, 

I already have a patch that does this and planed to submit it once this
one is in. The reason I stared digging around readnow_function is that
search-via-psyms series broke my "Python JIT API" code as well as JIT 
reader precisely because they do not install any quick functions.

Maybe better way to go about it might be:

 1) introduce new quick functions, say "default_symbol_functions" with
    the code from this (V2) series.
 2) then DWARF's readnow_functions may inherit from "default_symbol_functions"
    and override what's desirable

and then JIT reader would just use these new "default_symbol_functions".

> the
> DWARF reader could subclass it to just add the one new method.
> 
> This way the message would still arrive at the right time, which seems
> friendlier to users.
> 
> Jan> This commit therefore checks if there are any unexpanded CUs and if
> Jan> so, prints "Expanding full..." message as before. If all CUs are already
> Jan> expanded, say just "Expanded full...".
> 
> Also if there are multiple debug readers for an objfile, we could get
> the "wrong" message here through no fault of the reader itself, if that
> makes sense.

I'm lost. In what situation we'd get "wrong" message?

Thanks! 
Jan

> 
> Tom


  reply	other threads:[~2025-12-02 18:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 19:55 [PATCH v2 00/13] reimplement readnow_functions Jan Vrany
2025-11-24 19:55 ` [PATCH v2 01/13] gdb: reimplement readnow_functions::search Jan Vrany
2025-12-02 17:25   ` Tom Tromey
2025-11-24 19:55 ` [PATCH v2 02/13] gdb: implement readnow_functions::has_symbols Jan Vrany
2025-11-24 19:55 ` [PATCH v2 03/13] gdb: implement readnow_functions::has_unexpanded_symtabs Jan Vrany
2025-11-24 19:55 ` [PATCH v2 04/13] gdb: implement readnow_functions::find_last_source_symtab Jan Vrany
2025-11-24 19:55 ` [PATCH v2 05/13] gdb: implement readnow_functions::forget_cached_source_info Jan Vrany
2025-11-24 19:55 ` [PATCH v2 06/13] gdb: implement readnow_functions::lookup_global_symbol_language Jan Vrany
2025-11-24 19:55 ` [PATCH v2 07/13] gdb: implement readnow_functions::print_stats Jan Vrany
2025-11-24 19:55 ` [PATCH v2 08/13] gdb: implement readnow_functions::expand_all_symtabs Jan Vrany
2025-11-24 19:55 ` [PATCH v2 09/13] gdb: implement readnow_functions::find_pc_sect_compunit_symtab Jan Vrany
2025-11-24 19:55 ` [PATCH v2 10/13] gdb: implement readnow_functions::map_symbol_filenames Jan Vrany
2025-11-24 19:55 ` [PATCH v2 11/13] gdb: make readnow_functions to inherit from quick_symbol_functions Jan Vrany
2025-11-24 19:55 ` [PATCH v2 12/13] gdb/testsuite: fix few tests after change in readnow_functions Jan Vrany
2025-12-02 17:26   ` Tom Tromey
2025-11-24 19:55 ` [PATCH v2 13/13] gdb: update message in symbol_file_add_with_addrs after changes " Jan Vrany
2025-12-02 17:29   ` Tom Tromey
2025-12-02 18:48     ` Jan Vraný [this message]
2025-12-02 18:57       ` Tom Tromey
2025-12-02 19:03       ` Tom Tromey
2025-12-03 17:46         ` Jan Vraný
2025-12-02 13:39 ` [PATCH v2 00/13] reimplement readnow_functions Jan Vraný

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=576dde3ff5c99574ff024b6590c255ea356b1a1b.camel@labware.com \
    --to=jan.vrany@labware.com \
    --cc=gdb-patches@sourceware.org \
    --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