From: David Blaikie <dblaikie@gmail.com>
To: "R. Diez" <rdiezmail-binutils@yahoo.de>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Greatly increased GDB memory and CPU usage with newest embedded ARM toolchain
Date: Sun, 18 Apr 2021 08:41:04 -0700 [thread overview]
Message-ID: <CAENS6EvKN_FvFvhZxdJzBPpT2Xzx1RCttDZ6sK3swxqWrFLTPw@mail.gmail.com> (raw)
In-Reply-To: <fde10560-fff2-3dc6-117f-0237657864ea@yahoo.de>
Yeah, that checks out then. (you can also confirm that SHF_COMPRESSED
is not used by readelf -S or llvm-readelf -S and checking for the "C"
value in the Flags column)
& yeah, that does seem like quite a bit of RAM usage for a relatively
small amount of debug info. Though I'm not a regular/frequent gdb
developer, so I don't have any particular insight there - if no one
else chimes in, might be worth running valgrind --tool=massif to get a
memory profile, might point to what part of gdb is using all the RAM.
On Sun, Apr 18, 2021 at 1:16 AM R. Diez <rdiezmail-binutils@yahoo.de> wrote:
>
>
> >> The debug information is not compressed.
> >
> > How are you determining that ^ ?
> >
> > (I ask, because historically compressed debug info was opt-in and used
> > a section name mangling (.zdebug_*) to notate compressed debug
> > sections - but recent versions of GCC have started compressing by
> > default and using an ELF section flag (SHF_COMPRESSED) without section
> > name mangling (so dumping section names would not be enough to
> > determine whether compressed debug info was used)
>
>
> I do not know about SHF_COMPRESSED.
>
> I checked with:
>
> $ ./arm-none-eabi-ld --help
>
> [...]
> --compress-debug-sections=[none|zlib|zlib-gnu|zlib-gabi]
> Compress DWARF debug sections using zlib
> Default: none
> [...]
>
>
> I did not quite trust the "Default: none" statement, so I tested in the past by passing the following flag:
>
> -Wl,--compress-debug-sections=zlib
>
> And the resulting elf file was less than half the size.
>
> That is how I assume that the debug information is not being compressed.
>
> I am not compressing because for such a little project it is not worth it.
>
> Regards,
> rdiez
next prev parent reply other threads:[~2021-04-18 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <537840208.5089288.1618695042450.ref@mail.yahoo.com>
2021-04-17 21:30 ` R. Diez
2021-04-17 22:15 ` David Blaikie
2021-04-18 8:16 ` R. Diez
2021-04-18 15:41 ` David Blaikie [this message]
[not found] ` <95f8714b-a105-8759-dcc4-73122ee8bcf2@yahoo.de>
2021-04-19 4:57 ` David Blaikie
2021-04-19 5:10 ` David Blaikie
2021-04-19 16:08 ` R. Diez
2021-04-19 7:06 ` R. Diez
2021-04-19 1:07 ` Simon Marchi
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=CAENS6EvKN_FvFvhZxdJzBPpT2Xzx1RCttDZ6sK3swxqWrFLTPw@mail.gmail.com \
--to=dblaikie@gmail.com \
--cc=gdb@sourceware.org \
--cc=rdiezmail-binutils@yahoo.de \
/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).