Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Do not add partial_symbol again and again to the list
Date: Tue, 12 Feb 2008 02:12:00 -0000	[thread overview]
Message-ID: <20080212021156.GA15744@caradoc.them.org> (raw)
In-Reply-To: <47B0F16B.9090308@qnx.com>

On Mon, Feb 11, 2008 at 08:07:55PM -0500, Aleksandar Ristovski wrote:
> struct dwarf2_cu has a pointer to struct objfile, which (if I'm not 
> mistaken) get's allocated per compilation unit.

That's where your confusion is.  An objfile is something like
"/lib/libc.so.6", a linked file.  A compilation unit is something
like "init.o", a single "gcc -c" output.

Look at how n_static_syms is set in dwarf2read.c to see how
multiple psymtabs, for different CUs, share the same static_psymbols
list.

>>> Not sure if it is a valid indicator but I didn't have any regressions 
>>> in 'make check'.
>>
>> Yeah, I think I could write some testcases that were affected by this,
>> but I'm not sure.  It's tricky because if something else causes the
>> full symtab to load, the problem won't appear.
>
> Yes, that is the tricky part. We want lookup by symbol name to occur in 
> order to test this. Maybe adding a maintenance command that would 
> explicitly lookup a partial symbol by name?

The trick for writing testcases is to not stop in the second file or
"list" it or set a breakpoint in it; any of those things will load the
symtab.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-02-12  2:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 20:23 Aleksandar Ristovski
2008-02-11 20:38 ` Daniel Jacobowitz
2008-02-11 20:52   ` Aleksandar Ristovski
2008-02-11 21:09     ` Daniel Jacobowitz
2008-02-11 21:41       ` Aleksandar Ristovski
2008-02-11 21:48         ` Daniel Jacobowitz
2008-02-11 22:10           ` Aleksandar Ristovski
2008-02-11 22:31             ` Daniel Jacobowitz
2008-02-11 22:43               ` Aleksandar Ristovski
2008-02-11 22:53                 ` Daniel Jacobowitz
2008-02-12  1:08                   ` Aleksandar Ristovski
2008-02-12  2:12                     ` Daniel Jacobowitz [this message]
2008-02-12  5:35                       ` Aleksandar Ristovski
2008-02-12 13:26                         ` Daniel Jacobowitz
2008-02-12 15:54                           ` Aleksandar Ristovski
2008-02-13  5:23                   ` Aleksandar Ristovski
2008-02-14  1:31                     ` Aleksandar Ristovski
2008-05-02 18:11                       ` Aleksandar Ristovski
2008-05-03 21:32                     ` Daniel Jacobowitz
2008-05-05 19:41                       ` Aleksandar Ristovski
2008-05-05 19:38                         ` Aleksandar Ristovski
2008-05-06 15:47                         ` Daniel Jacobowitz
2008-05-06 18:45                           ` Aleksandar Ristovski
2008-05-06 18:39                             ` Aleksandar Ristovski
2008-05-06 18:50                             ` Daniel Jacobowitz
2008-05-07  8:22                               ` Aleksandar Ristovski
2008-05-07  9:01                                 ` Aleksandar Ristovski
2008-06-05 18:17                                 ` Daniel Jacobowitz
2008-06-05 19:26                                   ` Aleksandar Ristovski

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=20080212021156.GA15744@caradoc.them.org \
    --to=drow@false.org \
    --cc=aristovski@qnx.com \
    --cc=gdb-patches@sourceware.org \
    /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