Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/symbol readers] Clean up setting symbols' names
Date: Mon, 16 Feb 2004 20:59:00 -0000	[thread overview]
Message-ID: <20040216205941.GA16546@nevyn.them.org> (raw)
In-Reply-To: <16433.11537.105919.97207@localhost.redhat.com>

On Mon, Feb 16, 2004 at 03:50:25PM -0500, Elena Zannoni wrote:
> Daniel Jacobowitz writes:
>  > This patch does a couple of related things.
>  > 
>  > 1.  It adds a macro, SYMBOL_SET_LINKAGE_NAME, which is used to set a
>  > symbol's name when the name should not be demangled.  Used for things like
>  > typedefs whose name comes from debug info.  I did not change anything
>  > related to memory allocation when I did this - though in hpread I found a
>  > few inconsistencies.
>  > 
>  > 2.  It makes hpread use SYMBOL_SET_NAMES.  It contained some fallback code
>  > to use the debug info if demangling failed; I've disabled it, because from
>  > the description it sounds like the right thing to do would be to fix the
>  > demangler instead.  I can't tell whether the code is currently used or not,
>  > so I would appreciate HP/UX testing for this patch.
>  > 
>  > In the process I also kill a couple of DEPRECATED_SYMBOL_NAME uses, and the
>  > redundant function add_psymbol_with_dem_name_to_list.
>  > 
>  > No testsuite changes with DWARF2 or stabs+ on i386-linux.  OK?
>  > 
> 
> NO. There are way too many unrelated changes in this patch.
> 
> The changes to hpread to use SYMBOL_SET_NAMES should be
> independent. However you are also changing the logic of the code in a
> few places, not just mechanically replacing things. You are changing
> printf's, deleting functions, etc etc. You say there are no regression
> on i386-linux, did you test on hpux?

No.  Fancy that, that's why I asked for someone to do so.  I don't have
any way to test on HP/UX; the last time I tried to set up a test
environment on the testdrive systems it took me a week and a half to
get a baseline.  The last time I tried to use it they'd upgraded
libraries and none of my binaries worked.

> The objfiles and symfile changes are also logically separate. 
> The SYMBOL_SET_LINKAGE_NAME macro can also be a separate thing.
> 
> I shouldn't spend time reminding you of this.

I fail to see how the symfile change is independent of anything, since
the function is still used before my patch.  I'll break the patch in
thirds with splitdiff and test the thirds.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2004-02-16 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 19:35 Daniel Jacobowitz
2004-02-16 20:54 ` Elena Zannoni
2004-02-16 20:59   ` Daniel Jacobowitz [this message]

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=20040216205941.GA16546@nevyn.them.org \
    --to=drow@false.org \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.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