Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Doug Evans <dje@google.com>
Cc: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [RFC] Cleanup for make_source_files_completion_list
Date: Wed, 15 May 2013 17:36:00 -0000	[thread overview]
Message-ID: <5193C786.4000207@redhat.com> (raw)
In-Reply-To: <519156F5.5090000@redhat.com>

On 05/13/2013 02:11 PM, Keith Seitz wrote:
> On 05/13/2013 11:42 AM, Keith Seitz wrote:
>> However, I think that the comment quoted above (and the surrounding
>> block of code which does the copying) should be removed and the callers
>> of make_source_files_completion list should pass text AND word instead
>> of text and text. add_filename_to_list (in symtab.c) does this text -
>> word adjustment already, so it is not necessary to repeat it here. WDYT?
>
> Something like this? [This causes no regressions in the test suite or by
> manually hacking at it.]

Ok, no, this won't work either. The text in the comment (which I 
proposed to remove) hints at the problem:

$ cat same.c
int
same (int a)
{
    return a;
}

int
main (void)
{
   return same (0);
}
$ gcc -g same.c -o same
$ gdb -q same
(gdb) b same.\t\t
[blah blah blah]
c
same
(gdb)

Compare this with unpatched gdb:
(gdb) b same.\t\t
[blah blah blah]
same.c
same

So this needs to stay put. I'll see if I can generate a test case for this.

Thanks to Tom for bringing this up.

Keith


  reply	other threads:[~2013-05-15 17:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 19:46 Keith Seitz
2013-05-09 20:58 ` Tom Tromey
2013-05-09 23:45 ` Doug Evans
2013-05-13 18:42   ` Keith Seitz
2013-05-13 21:11     ` Keith Seitz
2013-05-15 17:36       ` Keith Seitz [this message]
2013-05-15 19:32         ` [RFA] completer test [was Re: [RFC] Cleanup for make_source_files_completion_list] Keith Seitz
2013-05-15 20:01           ` Tom Tromey
2013-05-15 21:22             ` Keith Seitz
2013-05-15 22:33           ` Sergio Durigan Junior
2013-05-15 23:47             ` Keith Seitz
2013-05-16  0:21               ` Sergio Durigan Junior
2013-05-16  0:27               ` Stan Shebs
2013-05-16  9:38                 ` Pedro Alves
2013-05-16  5:30               ` Joel Brobecker
2013-05-16  5:49                 ` Joel Brobecker
2013-05-16 15:41                   ` Keith Seitz
2013-05-17  5:14                     ` Joel Brobecker
2013-05-17 16:27                       ` Tom Tromey
2013-05-20  5:28                         ` Joel Brobecker
2013-05-20 14:47                           ` Tom Tromey
2013-05-21  5:43                             ` Checked in: " Joel Brobecker
2013-05-21  5:44                               ` Joel Brobecker
2013-05-16  5:53                 ` Sergio Durigan Junior
2013-05-16  6:00                   ` Joel Brobecker
2013-05-16  9:19               ` Pedro Alves
2013-05-16  9:26                 ` Joel Brobecker
2013-05-16 10:18                   ` 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=5193C786.4000207@redhat.com \
    --to=keiths@redhat.com \
    --cc=dje@google.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