Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Andrei Warkentin <andreiw@motorola.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Symbol file scope?
Date: Tue, 31 May 2011 17:09:00 -0000	[thread overview]
Message-ID: <m3k4d6ssqb.fsf@fleche.redhat.com> (raw)
In-Reply-To: <BANLkTimdA21_Td4kqec5nKVnVoWCytwO6Q@mail.gmail.com> (Andrei	Warkentin's message of "Fri, 27 May 2011 18:14:06 -0500")

>>>>> "Andrei" == Andrei Warkentin <andreiw@motorola.com> writes:

Andrei> It would be nice to be able to
Andrei> have globals be searched for first in the object file to which the
Andrei> current scope is in. Additionally, it would be nice to be able to
Andrei> implement "module scope" in the same fashion as "file scope", so you
Andrei> can look at globals in any module like this -

Andrei> (gdb) print &'DxeCore.dll'::gST
Andrei> $15 = (EFI_SYSTEM_TABLE **) 0x17fca6f0
Andrei> (gdb) print &'IsaBusDxe.dll'::gST
Andrei> $16 = (EFI_SYSTEM_TABLE **) 0x17e21da4

This seems like a good feature.

Andrei> 1) Modifies lookup_symbol_global to use
Andrei> lookup_global_symbol_from_objfile before lookup_symbol_aux_symatbs or
Andrei> solib_global_lookup
Andrei> 2) Modifies lookup_symtab to match symbol object file as well. It
Andrei> returns the first symtab, which is good enough for
Andrei> lookup_symbol_global logic to work. (I basically wanted to avoid
Andrei> modifying c-exp, p-exp, etc, parsers)

I'd have to see it and hear more rationale for the placement.
Offhand it seems reasonable.

Andrei> 3) Fixes location completion to match object file names as well.

Thanks.

Andrei> 4) Adds a list-symbol-files command to list all objfiles and their
Andrei> locations, or list only those that match objfile/source file names.
Andrei> I.e -
Andrei> gdb) list-symbol-files DiskIo.c Dispatcher.c EhciDxe.dll

This should be an "info" subcommand instead.

Andrei> I have a patch here -
Andrei> https://github.com/andreiw/andreiw-wip/blob/master/gdb/0001-GDB-Initial-prototype-of-symbol-file-scope-module-sc.patch

I glanced at it but didn't try to do any serious review.
I'd suggest: rebase, write a ChangeLog entry, and submit here.
You'll also have to update the docs and write some tests.

If you don't have copyright assignment paperwork in place, please
contact me off-list so we can get you started on that.  It is best to
start this early, because sometimes it takes a while.

Tom


  reply	other threads:[~2011-05-31 17:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 23:14 Andrei Warkentin
2011-05-31 17:09 ` Tom Tromey [this message]
2011-05-31 18:43   ` Andrei Warkentin

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=m3k4d6ssqb.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=andreiw@motorola.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