public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Weimin Pan <weimin.pan@oracle.com>
To: Tom Tromey <tom@tromey.com>
Cc: Weimin Pan via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH,V4 2/2] CTF: multi-CU and archive support
Date: Mon, 10 May 2021 17:33:32 -0700	[thread overview]
Message-ID: <1211c941-b6d9-a721-893b-aff31f8a5225@oracle.com> (raw)
In-Reply-To: <87y2cm8ejz.fsf@tromey.com>


On 5/10/2021 2:27 PM, Tom Tromey wrote:
>>>>>> ">" == Wei-min Pan <weimin.pan@oracle.com> writes:
>>> Thank you for taking the time. Please see below for some explanation
>>> about CTF and let me know if you need more info.
> Thank you.
>
>>> Where each archive has the CU as its name and ".ctf" as its parent's name
>>> (emitted by the linker.) In terms of psymtabs, there is only one parent
>>> which can have any number of archives.
> I think this will probably yield over-expansion in gdb.  What I mean is
> that if any symbol is found in CTF, all types and symbols will be
> expanded.  Normally this isn't what you want, though -- you only really
> need or want to expand the psymtab that has the type (or whatever) that
> was asked for.
>
> Normally what you want is for a single psymtab to correspond to a single
> source file.  In gdb the dependencies are used for #includes, which I
> guess comes from how stabs were originally implemented.

Yes, that's what happens with the CTF layout. While there is some
benefit of generating psymtabs, it's quite limited as you pointed out.
And I doubt that even getting rid of emitting psymtabs altogether
will not help much. Do you have any suggestions?

Thanks.

>
> Tom

  reply	other threads:[~2021-05-11  0:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27  1:00 [PATCH,V4 0/2] CTF: bug fixes and new features Weimin Pan
2021-04-27  1:00 ` [PATCH,V4 1/2] CTF: fix incorrect function return type Weimin Pan
2021-04-27  1:00   ` [PATCH,V4 2/2] CTF: multi-CU and archive support Weimin Pan
2021-05-07 20:29     ` Tom Tromey
2021-05-10  3:11       ` Wei-min Pan
2021-05-10 21:27         ` Tom Tromey
2021-05-11  0:33           ` Weimin Pan [this message]
2021-05-11 18:58           ` Weimin Pan
2021-05-13 17:21             ` Tom Tromey
2021-05-13 21:40               ` Wei-min Pan
2021-05-08 20:13     ` Tom Tromey
2021-05-10  3:12       ` Wei-min Pan
2021-05-07 20:07   ` [PATCH,V4 1/2] CTF: fix incorrect function return type Tom Tromey
2021-05-10  2:40     ` Wei-min Pan
2021-05-10 14:00       ` Tom Tromey
2021-05-16 22:31     ` Wei-min Pan

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=1211c941-b6d9-a721-893b-aff31f8a5225@oracle.com \
    --to=weimin.pan@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).