Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: S?bastien Granjoux <seb.sfo@free.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix breakpoints when several source files have the same name
Date: Mon, 09 Nov 2009 21:09:00 -0000	[thread overview]
Message-ID: <20091109210849.GS4557@adacore.com> (raw)
In-Reply-To: <4AF87BF4.5040303@free.fr>

Sebastien,

Would you mind sending unified diffs, next time.  There seems to be
a preference of unified diffs over context diffs.  (thank you!)

2009-10-29  Sebastien Granjoux <seb.sfo@free.fr>

	PR mi/9583:
	* symtab.c (find_line_symtab, append_exact_match_to_sals)
	(expand_line_sal): Use full filename when setting breakpoints if
	available

This is OK with one minor comment:

>   /* Helper to expand_line_sal below.  Search in the symtabs for any
> !    linetable entry that exactly matches FILENAME and LINENO and append
> !    them to RET. If there is at least one match, return 1; otherwise,
> !    return 0, and return the best choice in BEST_ITEM and BEST_SYMTAB.  */
>   
>   static int
> ! append_exact_match_to_sals (char *filename, int lineno,
>   			    struct symtabs_and_lines *ret,
>   			    struct linetable_entry **best_item,
>   			    struct symtab **best_symtab)
> --- 4598,4611 ----
>   }
>   
>   /* Helper to expand_line_sal below.  Search in the symtabs for any
> !    linetable entry that exactly matches FULLNAME and LINENO and append
> !    them to RET. If FULLNAME is NULL or if a symbol has no full name,
> !    use FILENAME and LINENO instead. If there is at least one match,
> !    return 1; otherwise, return 0, and return the best choice in BEST_ITEM
> !    and BEST_SYMTAB.  */

Periods need to be followed by 2 spaces (GNU Coding Standards). I realize
that the text you started with had the problem too!  Also, I believe there
is a typo "symbol has no full name" -> "symtab has no full name"?

Pre-approved with the changes above.  Have your assignment request
come through, yet?

-- 
Joel


  reply	other threads:[~2009-11-09 21:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 20:31 Sébastien Granjoux
2009-11-09 21:09 ` Joel Brobecker [this message]
2009-11-09 21:38   ` Sébastien Granjoux
2009-11-09 22:05     ` Joel Brobecker
2009-11-10 18:46       ` Sébastien Granjoux
  -- strict thread matches above, loose matches on Subject: below --
2009-10-29 21:55 Sébastien Granjoux
2009-10-01 21:05 Sébastien Granjoux
2009-10-01 21:45 ` Joel Brobecker
2009-10-02 20:28   ` Sébastien Granjoux
2009-05-24 10:49 Sébastien Granjoux
2009-09-29 22:20 ` Joel Brobecker
2009-09-30 18:53   ` Sébastien Granjoux
2009-09-30 19:07     ` Jan Kratochvil

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=20091109210849.GS4557@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=seb.sfo@free.fr \
    /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