From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Keith Seitz <keiths@redhat.com>,
"gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>,
Yao Qi <yao@codesourcery.com>
Subject: Re: [RFC] breakpoints/19474 [was Re: RFC: branching for GDB 7.11 soon? (possibly Wed)]
Date: Fri, 12 Aug 2016 12:00:00 -0000 [thread overview]
Message-ID: <CAH=s-PPgN2YhEZ2iz5ck2pNWR+UPAFTLT5mk8KpVedo3WN7Tjg@mail.gmail.com> (raw)
In-Reply-To: <56B344A5.1060406@redhat.com>
Hi Keith,
Are you still working on this patch? This problem bites me again in the 7.12
testing, and that leads me digging out this patch. I don't think we need to
pick it up in 7.12, but it's better to pick it in master after 7.12
release, so that
we have a plenty of time to see how good (or bad) it is.
On Thu, Feb 4, 2016 at 12:31 PM, Pedro Alves <palves@redhat.com> wrote:
> On 02/04/2016 12:45 AM, Keith Seitz wrote:
>
>> At Pedro's urging, I found another, simpler solution. The big problem
>> with just about all solutions I was attempting to implement is
>> [p]symtab_to_fululname/find_and_open_source/openp. These functions are
>> just completely unaware of what the caller is attempting to do.
>
> Thanks!
>
>
>> I'm sure there are corner cases and a whole bunch of other problems with
>> this approach, but at least it is isolated to one place (for better or
>> worse).
>
> Things to watch out for, out of the blue:
>
> - relative SYMTAB_DIRNAMEs -- is there such a thing?
>
> - symlinks. Say, what happens if foo/f.c is a symlink to f.c (perhaps
> each is compiled differently, with -DWHATNOT, for example).
>
>> +static VEC (symtab_ptr) *
>> +filter_default_symtabs (const char *fullname, VEC (symtab_ptr) *symtabs)
>> +{
>> + int ix;
>> + struct symtab *symtab;
>> + VEC (symtab_ptr) *filtered_symtabs = NULL;
>> + struct cleanup *back_to = make_cleanup (null_cleanup, NULL);
>
> I think filtered_symtabs should be guarded with a cleanup as well.
>
>> +
>> + /* Iterate through the symtabs, searching for matches to FULLNAME. */
>> + for (ix = 0; VEC_iterate (symtab_ptr, symtabs, ix, symtab); ++ix)
>> + {
>> + const char *basename = lbasename (fullname);
>> + char *symtab_with_dir;
>> +
>> + if (SYMTAB_DIRNAME (symtab) == NULL)
>> + continue;
>> +
>> + symtab_with_dir = concat (SYMTAB_DIRNAME (symtab), SLASH_STRING,
>> + basename, NULL);
>> + make_cleanup (xfree, symtab_with_dir);
>> + if (streq (fullname, symtab_with_dir))
>> + VEC_safe_push (symtab_ptr, filtered_symtabs, symtab);
>> + else
>> + {
>> + /* Now try any path substitution rules. */
>> + symtab_with_dir = rewrite_source_path (symtab_with_dir);
>> + if (symtab_with_dir != NULL)
>> + {
>> + make_cleanup (xfree, symtab_with_dir);
>> + if (streq (fullname, symtab_with_dir))
>> + VEC_safe_push (symtab_ptr, filtered_symtabs, symtab);
>> + }
>> + }
>
> This creates two cleanups per iteration here. Only two for the whole
> loop would suffice, if you used free_current_contents instead of xfree.
>
>> + }
>> +
>> + /* If we found no matches, use whatever symtabs were originally
>> + "collected." */
>> + if (filtered_symtabs == NULL)
>
> Pedantically, checking VEC_empty instead would be better, as an initial
>
> VEC_reserve (symtab_ptr, filtered_symtabs, VEC_size (symtab_ptr, symtab));
>
> would make a NULL check wrong. That reserve might make sense if most of
> the time we'll match all symtabs.
>
>> + {
>> + /* Found no exact matches -- use the original list. */
>> + filtered_symtabs = symtabs;
>> + }
>> + else
>> + VEC_free (symtab_ptr, symtabs);
>> +
>> + do_cleanups (back_to);
>> + return filtered_symtabs;
>> +}
>
> Thanks,
> Pedro Alves
>
--
Yao (齐尧)
next prev parent reply other threads:[~2016-08-12 12:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 3:06 RFC: branching for GDB 7.11 soon? (possibly Wed) Joel Brobecker
2016-02-01 13:34 ` Pedro Alves
2016-02-01 17:04 ` Pedro Alves
2016-02-01 19:51 ` Keith Seitz
2016-02-04 0:45 ` [RFC] breakpoints/19474 [was Re: RFC: branching for GDB 7.11 soon? (possibly Wed)] Keith Seitz
2016-02-04 1:33 ` Keith Seitz
2016-02-04 11:05 ` Yao Qi
2016-02-04 12:31 ` Pedro Alves
2016-08-12 12:00 ` Yao Qi [this message]
2016-02-07 8:12 ` RFC: branching for GDB 7.11 soon? (possibly Wed) Joel Brobecker
2016-02-08 18:03 ` Sergio Durigan Junior
2016-02-08 19:28 ` Keith Seitz
2016-02-08 20:06 ` Pedro Alves
2016-02-08 20:11 ` Keith Seitz
2016-02-09 5:35 ` Sergio Durigan Junior
2016-02-09 14:15 ` Simon Marchi
2016-02-09 14:18 ` Pedro Alves
2016-02-09 14:52 ` Simon Marchi
2016-02-09 18:31 ` Sergio Durigan Junior
2016-02-09 11:56 ` Joel Brobecker
2016-02-09 12:37 ` Pedro Alves
2016-02-09 22:37 ` Keith Seitz
2016-02-10 3:40 ` Joel Brobecker
2016-02-10 10:04 ` Pedro Alves
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='CAH=s-PPgN2YhEZ2iz5ck2pNWR+UPAFTLT5mk8KpVedo3WN7Tjg@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=palves@redhat.com \
--cc=yao@codesourcery.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