Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb.dwarf2: Define and use gdb_target_symbol_prefix for symbol prefixes
Date: Fri, 30 Oct 2015 15:53:00 -0000	[thread overview]
Message-ID: <56335065.1060100@redhat.com> (raw)
In-Reply-To: <20151029222505.3bb590b9@pinnacle.lan>

On 10/30/2015 05:25 AM, Kevin Buettner wrote:
> On Thu, 29 Oct 2015 21:25:09 -0700
> Kevin Buettner <kevinb@redhat.com> wrote:
> 
>> Some of the tests in gdb.dwarf2 which use Dwarf::assemble refer to
>> (minimal/linker) symbols created in the course of building a small
>> test program.  Some targets use a prefix such as underscore ("_") on
>> these symbols.  Many of the tests in gdb.dwarf2 do not take this into
>> account.  As a consequence, these tests fail to build, resulting
>> either in failures or untested testcases.
> 
> Several of the .S files in gdb.dwarf2 have the same problem.  E.g.
> when linking the test case for gdb.dwarf2/method-ptr.exp, I see a
> linker error "undefined reference to `main'".  It appears that crt0
> is generating a reference to _main, but the .S file only provides a
> reference to main.
> 
> Any thoughts on what to do about this?

Isn't this being addressed by gdb_target_symbol_prefix_flags in
the existing tests that use it?  E.g., gdb.arch/i386-bp_permanent.c:

#ifdef SYMBOL_PREFIX
#define SYMBOL(str)     SYMBOL_PREFIX #str
#else
#define SYMBOL(str)     #str
#endif

...

#ifdef __x86_64__
asm(".text\n"
    "    .align 8\n"
    SYMBOL (standard) ":\n"

Thanks,
Pedro Alves


  reply	other threads:[~2015-10-30 11:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 11:06 Kevin Buettner
2015-10-30 12:06 ` Kevin Buettner
2015-10-30 15:53   ` Pedro Alves [this message]
2015-11-05  6:39     ` Kevin Buettner
2015-11-05 10:46       ` Pedro Alves
2015-11-05 10:55         ` Pedro Alves
2015-11-06  5:33           ` Kevin Buettner
2015-10-30 15:51 ` Pedro Alves
2015-11-04 21:49   ` Kevin Buettner
2015-11-05 10:14     ` Pedro Alves
2015-11-05 20:01       ` Kevin Buettner
2015-11-05 21:19         ` Pedro Alves
2015-11-05 22:26           ` Kevin Buettner

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=56335065.1060100@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@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