From: Omair Javaid <omair.javaid@linaro.org>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite/gdb.dwarf2: Fix for dw2-ifort-parameter failure on ARM
Date: Thu, 16 Jan 2014 10:26:00 -0000 [thread overview]
Message-ID: <52D7B3C5.1000702@linaro.org> (raw)
In-Reply-To: <52D7AAF1.80501@redhat.com>
On 01/16/2014 02:48 PM, Pedro Alves wrote:
> On 01/16/2014 09:03 AM, Omair Javaid wrote:
>
>> There seemed no problem with how breakpoint addresses were being adjusted.
>> This test requires to build dwarf info by hand in dw2-ifort-parameter-debug.S
>> using compile time addresses so in case of arm (thumb mode) the least
>> significant bits of compile time address are set to 1. For that reason
>> 0x000083bd was being used as a breakpoint address func.
>
> OOC, what does the compiler debug info usually do instead to avoid this?
>
Here is what compiler generates when there are thumb functions to handle:
.thumb_func
.type func, %function
func:
.LFB0:
func is marked as thumb function and thus this func pointer will have the
lower bit set. While .LFB0: non thumb label will be used to mark function
start address. Like this: .4byte .LFB0 @ DW_AT_low_pc
next prev parent reply other threads:[~2014-01-16 10:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANW4E-2bQYjx6YdR3qGyKUsQa_KOrtmkWsZYqKzcuQBF==RPpw@mail.gmail.com>
2013-07-15 10:25 ` Omair Javaid
2013-07-16 2:53 ` Yao Qi
2013-09-19 15:31 ` Omair Javaid
2013-10-01 9:53 ` Omair Javaid
2013-11-11 9:53 ` Yao Qi
2014-01-16 9:09 ` Omair Javaid
2014-01-16 9:17 ` Will Newton
2014-01-16 9:48 ` Pedro Alves
2014-01-16 9:51 ` Pedro Alves
2014-01-16 10:26 ` Omair Javaid [this message]
2014-01-16 12:35 ` Pedro Alves
2014-01-16 13:55 ` Omair Javaid
2014-01-16 14:00 ` Pedro Alves
2014-01-16 14:17 ` Omair Javaid
2014-01-16 16:24 ` Pedro Alves
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=52D7B3C5.1000702@linaro.org \
--to=omair.javaid@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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