Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: vapier@gentoo.org
Cc: gdb-patches@sourceware.org, drow@false.org
Subject: Re: only force symbol lookups with local variables on hppa
Date: Tue, 22 Aug 2006 01:35:00 -0000	[thread overview]
Message-ID: <200608211829.k7LITfLB004305@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060820135754.GA17322@nevyn.them.org> (message from Daniel 	Jacobowitz on Sun, 20 Aug 2006 09:57:54 -0400)

> Date: Sun, 20 Aug 2006 09:57:54 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> On Sun, Aug 20, 2006 at 03:10:42PM +0200, Mark Kettenis wrote:
> > > From: Mike Frysinger <vapier@gentoo.org>
> > > Date: Sun, 20 Aug 2006 09:03:06 -0400
> > > 
> > > as a follow up to the slow script thread:
> > > http://sources.redhat.com/ml/gdb/2006-08/msg00099.html
> > > 
> > > attached patch will change the behavior so symbols with dollar signs
> > > in them0 ($) are only looked up when a specific arch says to do so
> > > (with hppa being the only one at the moment)
> > > -mike
> > 
> > > 2006-08-20  Mike Frysinger  <vapier@gentoo.org>
> > > 
> > > 	* parse.c (write_dollar_variable): Check LOOKUP_DOLLAR_SYMBOLS.
> > > 	* config/pa/tm-hppa.h [LOOKUP_DOLLAR_SYMBOLS]: Define.
> > 
> > Sorry but, this implementation is not acceptable; we want to get rid
> > of all the defines in tm.h files (and the files themselves
> > eventually), not add more :(.
> 
> As a followup, there are several better options:
> 
>   - Set a gdbarch hook.  See gdbarch.sh.
>   - Keep track of the number of symbols found which start with
>     a '$', probably in each objfile.  Only do the lookup if
>     symbols starting with dollar have been found.
>   - Just make partial symbol lookups faster.

And of these the last two are certainly preferable to the first
solution.

Actually, I'm afraid the assumption that symbols do not start with a
dollar sign isn't true on most platforms: I just created some
assembler code that contains such symbols and it assembles, links and
runs fine on OpenBSD/i386.  I have no doubt that the same will be true
on other ELF systems using the GNU toolchain.

Mark


  reply	other threads:[~2006-08-21 18:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-20 14:28 Mike Frysinger
2006-08-20 14:33 ` Mark Kettenis
2006-08-20 14:38   ` Daniel Jacobowitz
2006-08-22  1:35     ` Mark Kettenis [this message]
2006-08-22  2:06       ` Daniel Jacobowitz
2006-08-22 18:01     ` Mike Frysinger
2006-08-22 18:21       ` Daniel Jacobowitz
2006-08-22 18:34         ` Mike Frysinger
2006-09-14  5:01         ` [patch ping] change lookup order of $localvars to happen before symbol tables Mike Frysinger
2006-09-16  4:02           ` Daniel Jacobowitz
2006-09-17  4:22             ` Mike Frysinger
2006-09-17 15:10               ` Daniel Jacobowitz
2006-09-17 20:22                 ` Mike Frysinger
2006-09-17 20:28                   ` Daniel Jacobowitz
2006-09-27  5:51                 ` Mike Frysinger
2007-09-26 19:50                 ` Mike Frysinger
2007-10-01  0:37                   ` Daniel Jacobowitz
2007-10-01  1:41                     ` Mike Frysinger

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=200608211829.k7LITfLB004305@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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