public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>,  Kevin Buettner <kevinb@redhat.com>
Subject: Re: [PATCH] Throw error when creating an overly large gdb-index file
Date: Wed, 13 Sep 2023 08:24:02 -0600	[thread overview]
Message-ID: <87h6nyi22l.fsf@tromey.com> (raw)
In-Reply-To: <20230912194323.7537de96@f37-zws-nv> (Kevin Buettner via Gdb-patches's message of "Tue, 12 Sep 2023 19:43:23 -0700")

>>>>> "Kevin" == Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org> writes:

Kevin> The shared object is 3 GiB in size and the gdb-index section for it is
Kevin> 4.3 GiB in size.

Thanks.

Kevin> I extracted .debug_str using obj_copy, replaced the \0 characters
Kevin> with newlines, and then used sort and uniq on that output.  There
Kevin> were no duplicate lines.  Altogether, there are 1,212,620 strings
Kevin> in .debug_str.

Kevin> I can't say that I fully understand the layout of the constant pool,
Kevin> but it appears that all of the strings from .debug_str will end in the
Kevin> latter part of it.  So, if I'm right, that alone accounts for nearly
Kevin> half the size of the index file.

Yeah, putting copies into the constant pool was a mistake; though I
think part of my rationale was that often the constant pool will hold
different versions -- they go through name canonicalization.

Anyway your patch looks good to me.  Thank you.

Tom

  reply	other threads:[~2023-09-13 14:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09  2:55 Kevin Buettner
2023-09-09  5:19 ` Kevin Buettner
2023-09-09  8:20 ` Tom de Vries
2023-09-15  0:22   ` Kevin Buettner
2023-09-15  9:09     ` Tom de Vries
2023-09-12 16:07 ` Tom Tromey
2023-09-13  2:43   ` Kevin Buettner
2023-09-13 14:24     ` Tom Tromey [this message]
2023-09-15  0:10       ` Kevin Buettner

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=87h6nyi22l.fsf@tromey.com \
    --to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).