Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Keith Seitz <keiths@redhat.com>
Cc: "mihail.nistor@freescale.com" <mihail.nistor@freescale.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Bug 17394: we cannot put a break-point at a global function for ASM file
Date: Sat, 13 Dec 2014 13:04:00 -0000	[thread overview]
Message-ID: <20141213130429.GA12185@adacore.com> (raw)
In-Reply-To: <542B0854.6050804@redhat.com>

> gdb/ChangeLog:
> 2014-09-30  Keith Seitz  <keiths@redhat.com>
> 	    Mihail-Marian Nistor  <mihail.nistor@freescale.com>
> 
> 	PR gdb/17394
> 	* linespec.c (struct collect_minsyms): Add new member `symtab'.
> 	(add_minsym): Handle cases where info.symtab is non-NULL.
> 	(search_minsyms_for_name): Add new parameter `symtab'.
> 	Handle limiting searches to a specific symtab.
> 	(add_matching_symtabs_to_info): Search through minimal symbols
> 	for language_asm files for which no new symbols are found.
> 
> gdb/testsuite/ChangeLog:
> 2014-09-30  Mihail-Marian Nistor  <mihail.nistor@freescale.com>
> 
>       PR gdb/17394
>       * gdb.linespec/break-asm-file.c: New file.
>       * gdb.linespec/break-asm-file.exp: New file.
>       * gdb.linespec/break-asm-file0.s: New file.
>       * gdb.linespec/break-asm-file1.s: New file.

Overall, the patch looks good to me. Just a few trivial issues
hightlighted below, but the patch is otherwise approved.

> diff --git a/gdb/testsuite/gdb.linespec/break-asm-file.exp b/gdb/testsuite/gdb.linespec/break-asm-file.exp
> +
> +load_lib dwarf.exp 

Trailing space here...

> diff --git a/gdb/testsuite/gdb.linespec/break-asm-file0.s b/gdb/testsuite/gdb.linespec/break-asm-file0.s
[...]
> @@ -0,0 +1,218 @@
> +	.byte		1	/* DW_LNS_copy */
> +
> +  .byte		0	/* DW_LNE_set_address */

This file has a few .byte's where the formatting is inconsistent with
the rest. Not critical, but would you mind fixing those?


> +	.byte		1	/* DW_LNS_copy */
> +	

Trailing spaces...


> diff --git a/gdb/testsuite/gdb.linespec/break-asm-file1.s b/gdb/testsuite/gdb.linespec/break-asm-file1.s
[...]
> +	.byte		1	/* DW_LNS_copy */
> +	

Trailing spaces again...

> +	.byte		1	/* DW_LNS_copy */
> +	
Ditto...

> +	.4byte		.Lend_func
> +	

... and Ditto.

Thank you,
-- 
Joel


  parent reply	other threads:[~2014-12-13 13:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17 11:53 Mihail-Marian Nistor
2014-09-25 18:06 ` Keith Seitz
2014-09-28 15:47   ` mihail.nistor
2014-09-28 16:08     ` mihail.nistor
2014-09-30 19:45       ` Keith Seitz
2014-10-01 18:07         ` mihail.nistor
2014-12-13 13:04         ` Joel Brobecker [this message]
2014-12-15 20:47           ` mihail.nistor
2014-12-20 16:33             ` Joel Brobecker
2014-12-21  9:13               ` mihail.nistor

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=20141213130429.GA12185@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=mihail.nistor@freescale.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