From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] ENUM BITFIELD, here it comes again
Date: Thu, 21 Aug 2003 18:46:00 -0000 [thread overview]
Message-ID: <3F45136D.9060308@redhat.com> (raw)
In-Reply-To: <200308211742.h7LHgNJx028786@duracef.shout.net>
> + /* Rearranged: used ENUM_BITFIELD and rearranged field order in
> + all the space critical structures (plus struct minimal_symbol).
> + Memory usage dropped from 99360768 bytes to 90001408 bytes.
> + I measured this with before-and-after tests of
> + "HEAD-old-gdb -readnow HEAD-old-gdb" and
> + "HEAD-new-gdb -readnow HEAD-old-gdb" on native i686-pc-linux-gnu,
> + red hat linux 8, with LD_LIBRARY_PATH=/usr/lib/debug,
> + typing "maint space 1" at the first command prompt.
> + --chastain 2003-08-21 */
What effect does it have without -readnow but with say:
$ gdb gdb
(gdb) break internal_error
(gdb) run
(gdb) maint internal-error
(gdb) backtrace
which is kind of closer to the typical users:
$ gdb foo
(gdb) run
Segmentation fault
(gdb) bt
(gdb) list
(gdb) print pointer
$1 = 0
<bugger>
(gdb)^D
i.e., very few symbols are really loaded.
Andrew
next prev parent reply other threads:[~2003-08-21 18:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 17:42 Michael Elizabeth Chastain
2003-08-21 18:46 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-21 19:49 Michael Elizabeth Chastain
2003-08-21 18:57 Michael Elizabeth Chastain
2003-08-21 19:19 ` Andrew Cagney
2003-08-20 17:42 Michael Elizabeth Chastain
[not found] <200308201639.h7KGd6BX008220@duracef.shout.net>
2003-08-20 17:36 ` [rfa] ENUM_BITFIELD, " Jim Blandy
2003-08-20 16:49 [rfa] ENUM BITFIELD, " Michael Elizabeth Chastain
2003-08-21 13:48 ` Andrew Cagney
[not found] <200308200249.h7K2ni62029448@duracef.shout.net>
2003-08-20 7:52 ` [rfa] ENUM_BITFIELD, " Jim Blandy
2003-08-20 2:50 Michael Elizabeth Chastain
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=3F45136D.9060308@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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