From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Daniel Jacobowitz <drow@false.org>,
Tom Tromey <tromey@redhat.com>
Subject: type/main_type/field size [Re: [patch] static_kind -> bit0, bit1]
Date: Tue, 07 Oct 2008 23:22:00 -0000 [thread overview]
Message-ID: <20081007232111.GA6913@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20081006200928.GD3588@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Mon, 06 Oct 2008 22:09:28 +0200, Joel Brobecker wrote:
> I think it is kind of ugly, and i tried to think about it for a while,
> but I don't see many possible solutions if we don't want to increase
> the gdbtype struct size.
BTW are there some measurements if sizeof (type / main_type / field) matters?
On Tue, 07 Oct 2008 19:48:53 +0200, Tom Tromey wrote:
> For the lazy psymtab thing I had two related test cases:
>
> 1. Start OO.o writer, then time 'attach'.
> 2. The same, plus time "thread apply all bt full".
FYI I found (on Firefox) the difference of reading full symbols for this
command `thread apply all bt full' is:
valgrind --tool=massif:
mem_heap_B=393798138
mem_heap_B=395820353
== 2MB == only 0.5% size increase (by the attached patch if it is right)
Just `thread apply all bt full' may not be the typical debugging session,
a more representative application / command set would be useful.
Regards,
Jan
[-- Attachment #2: gdb-readneverfull.patch --]
[-- Type: text/plain, Size: 706 bytes --]
--- gdb/dwarf2read.c 30 Sep 2008 16:57:37 -0000 1.285
+++ gdb/dwarf2read.c 7 Oct 2008 20:50:07 -0000
@@ -2432,6 +2432,7 @@ locate_pdi_sibling (struct partial_die_i
static void
dwarf2_psymtab_to_symtab (struct partial_symtab *pst)
{
+return;
/* FIXME: This is barely more than a stub. */
if (pst != NULL)
{
--- gdb/symtab.c 1 Oct 2008 17:25:22 -0000 1.199
+++ gdb/symtab.c 7 Oct 2008 20:50:10 -0000
@@ -1527,6 +1527,8 @@ lookup_symbol_aux_psymtabs (int block_in
psymtab_index, domain))
{
s = PSYMTAB_TO_SYMTAB (ps);
+ if (!s)
+ continue;
bv = BLOCKVECTOR (s);
block = BLOCKVECTOR_BLOCK (bv, block_index);
sym = lookup_block_symbol (block, name, linkage_name, domain);
next prev parent reply other threads:[~2008-10-07 23:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 15:06 [gdb] Fortran dynamic arrays Tobias Burnus
2008-08-18 11:12 ` Joel Brobecker
2008-08-18 15:54 ` Ulrich Weigand
2008-09-07 11:59 ` [patch] static_kind -> bit0, bit1 [Re: [gdb] Fortran dynamic arrays] Jan Kratochvil
2008-09-08 15:32 ` Tom Tromey
2008-09-08 17:27 ` Jan Kratochvil
2008-09-19 22:29 ` Joel Brobecker
2008-09-26 23:04 ` Tom Tromey
2008-09-27 14:53 ` Joel Brobecker
2008-09-19 6:04 ` Joel Brobecker
2008-09-22 15:25 ` Jan Kratochvil
2008-09-24 19:15 ` Joel Brobecker
2008-09-26 5:03 ` Jan Kratochvil
2008-09-26 22:12 ` Joel Brobecker
2008-10-02 22:13 ` [patch] Fortran obsolete bounds type [Re: [patch] static_kind -> bit0, bit1] Jan Kratochvil
2008-09-26 12:52 ` [patch] static_kind -> bit0, bit1 [Re: [gdb] Fortran dynamic arrays] Daniel Jacobowitz
2008-09-26 22:15 ` Joel Brobecker
2008-09-26 22:20 ` Daniel Jacobowitz
2008-09-19 22:13 ` Joel Brobecker
2008-09-26 5:06 ` Accessor macro wrappers removal [Re: [patch] static_kind -> bit0, bit1] Jan Kratochvil
2008-09-26 12:55 ` Daniel Jacobowitz
2008-10-02 20:59 ` Jan Kratochvil
2008-10-02 21:05 ` Daniel Jacobowitz
2008-09-26 23:15 ` Tom Tromey
2008-09-26 12:58 ` [patch] static_kind -> bit0, bit1 [Re: [gdb] Fortran dynamic arrays] Daniel Jacobowitz
[not found] ` <20081006200928.GD3588@adacore.com>
2008-10-06 20:26 ` Jan Kratochvil
2008-10-07 23:22 ` Jan Kratochvil [this message]
2008-10-08 3:32 ` type/main_type/field size [Re: [patch] static_kind -> bit0, bit1] Joel Brobecker
2008-10-08 23:56 ` Tom Tromey
2008-10-04 20:28 ` [patch] static_kind -> bit0, bit1 [Re: [gdb] Fortran dynamic arrays] Jan Kratochvil
2008-10-06 20:00 ` Joel Brobecker
2008-10-07 23:18 ` Jan Kratochvil
2008-10-08 3:28 ` Joel Brobecker
2008-10-08 12:54 ` Jan Kratochvil
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=20081007232111.GA6913@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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