From: "mihail.nistor@freescale.com" <mihail.nistor@freescale.com>
To: Keith Seitz <keiths@redhat.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: Wed, 01 Oct 2014 18:07:00 -0000 [thread overview]
Message-ID: <5435dace65024022b64c7f86e1e37930@BN1PR0301MB0628.namprd03.prod.outlook.com> (raw)
In-Reply-To: <542B0854.6050804@redhat.com>
Thank you for everything. I'm looking forward to receiving the final approval so that the patch may be submitted.
Best regards,
Mihai
-----Original Message-----
From: Keith Seitz [mailto:keiths@redhat.com]
Sent: Tuesday, September 30, 2014 10:45 PM
To: Nistor Mihail-MNISTOR1; gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Bug 17394: we cannot put a break-point at a global function for ASM file
On 09/28/2014 09:08 AM, mihail.nistor@freescale.com wrote:
> -----Original Message-----
> From: Nistor Mihail-MNISTOR1
> Sent: Sunday, September 28, 2014 6:47 PM
> To: Keith Seitz; gdb-patches@sourceware.org
> Cc: Nistor Mihail-MNISTOR1
> Subject: RE: [PATCH v2] Bug 17394: we cannot put a break-point at a
> global function for ASM file
>
> Your changes look very well, I have one little observation regarding the filtering condition when we need to get information from minimal symbol.
> Scenario: We can mix objects that were compiled/assembled by different vendors and the third party assembler provides debug information and it doesn't have this limitation. An application may contain more than one file that have the same name. We cannot put a breakpoint at a function in all objects that have the same name if an object that comes from ASM file has debug info and is linked before the objects assembled with the GNU-GAS. In the new test case I have tried to emulate the third party assembler behavior in the break-asm-file1.s.
>
That makes sense to me. FWIW, here is a combined patch which I think a maintainer should give a final look over.
Thank you for the patch!
Keith
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.
next prev parent reply other threads:[~2014-10-01 18:07 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 [this message]
2014-12-13 13:04 ` Joel Brobecker
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=5435dace65024022b64c7f86e1e37930@BN1PR0301MB0628.namprd03.prod.outlook.com \
--to=mihail.nistor@freescale.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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