From: Tom Tromey <tromey@redhat.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: gdb-patches@sources.redhat.com, eliz@is.elta.co.il
Subject: Re: Patch: search `directory' path for `break' files
Date: Thu, 11 Oct 2001 20:46:00 -0000 [thread overview]
Message-ID: <87ofndjylo.fsf@creche.redhat.com> (raw)
In-Reply-To: <15301.63906.512294.33906@krustylu.cygnus.com>
>>>>> "Elena" == Elena Zannoni <ezannoni@cygnus.com> writes:
Elena> 1. Could you please check in the cleanup of lookup_symtab_1 as a
Elena> separate obvious fix?
Done.
Thanks for your reviews. I'll try soon to address the points you
raised and resubmit the patches. It might be a little while since any
gdb hacking I do is on my own time.
Elena> 2. I was about to approve your patch, which is ok, when I got
Elena> curious about why symtab_to_filename wasn't used
Elena> anywhere. Seeing it was introduced by Stu Grossman, I thought
Elena> of gdbtk, and voila' there it is. Have you looked at
Elena> gdbtk-cmds.c:full_lookup_symtab() ? Does it do what you need?
Elena> If so, could we avoid code duplication by having only one copy
Elena> of the same function?
I did run across this function after submitting my patch. I think my
patch obsoletes this function, and we can investigate removing it.
full_lookup_symtab() doesn't really do the same thing as my patch
though, at least as I understand it. I'm not 100% certain about what
is going on there since I don't know what the typical inputs to
full_lookup_symtab() look like.
When you say the patch is ok does that mean I can check in the rest of
it? Or should I try to handle psymtabs and directory names first?
Tom
next prev parent reply other threads:[~2001-10-11 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 16:45 Tom Tromey
2001-09-29 2:45 ` Eli Zaretskii
2001-10-01 13:52 ` Tom Tromey
2001-10-01 15:35 ` Michael Snyder
2001-10-02 1:01 ` Eli Zaretskii
2001-10-11 12:50 ` Elena Zannoni
2001-10-11 20:46 ` Tom Tromey [this message]
2001-10-14 14:43 ` Elena Zannoni
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=87ofndjylo.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=ezannoni@cygnus.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