Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix gdb.dwarf2/dwz.exp for thumb mode
Date: Sun, 14 Sep 2014 15:24:00 -0000	[thread overview]
Message-ID: <87ha0a6x95.fsf@igel.home> (raw)
In-Reply-To: <87bnqil1bb.fsf@codesourcery.com> (Yao Qi's message of "Sun, 14	Sep 2014 22:32:56 +0800")

Yao Qi <yao@codesourcery.com> writes:

> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>>> -if { $main_length == "" } {
>>> +set main_label_offset ""
>>> +set test "p main_label"
>>> +gdb_test_multiple $test $test {
>>> +    -re ".* = {.*} $hex <main\\+($decimal)>.*\r\n$gdb_prompt $" {
>>> +	set main_label_offset $expect_out(1,string)
>>> +    }
>>> +}
>>
>> This will also fail to match if assembler labels are prefixed.
>
> If you meant 'main' could be prefixed to '_main' for example, then GDB
> can get rid of the prefix on display.  On mingw target, function 'foo'
> is prefixed to '_foo', but GDB still shows 'foo' rather than '_foo'.

(gdb) p main_label 
$1 = {<text variable, no debug info>} 0x100004e0 <.main+12>

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2014-09-14 15:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-14 11:31 Andreas Schwab
2014-09-14 14:37 ` Yao Qi
2014-09-14 15:24   ` Andreas Schwab [this message]
2014-09-15  2:09     ` Yao Qi
2014-09-15  8:57       ` Andreas Schwab
  -- strict thread matches above, loose matches on Subject: below --
2014-09-03  1:23 Yao Qi
2014-09-03 17:51 ` Doug Evans
2014-09-05 11:08   ` Yao Qi
2014-09-14  9:35 ` Yao Qi
2014-09-15 12:29   ` Yao Qi
2014-09-22 13:52     ` Yao Qi
2014-09-30 14:04       ` Yao Qi
2014-10-07 14:03         ` Yao Qi

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=87ha0a6x95.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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