From: Prabhakar Kushwaha <prabhakar@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] config.mk:Update DBGFLAGS with dwarf information
Date: Tue, 19 Jun 2012 10:38:57 +0530 [thread overview]
Message-ID: <4FE00969.5070405@freescale.com> (raw)
In-Reply-To: <4FE00741.4040202@freescale.com>
Hi,
Sorry for the delayed response. I somehow missed this :(
On 06/19/2012 10:29 AM, Prabhakar Kushwaha wrote:
> Hi Prabhakar,
>
> On Thu, May 24, 2012 at 2:43 PM, Prabhakar Kushwaha
> <prabhakar@freescale.com> wrote:
> > Hi Wolfgang,
> >
> > This patch has been pending for a very long time. No review
> comments has
> > been provided.
>
> Mike Frysinger posted a comment on May 14, 2012:
>
> [quote]
> no real information here as to what is going wrong. the -g flag
> provides debug
> information and many people (myself included) have found this sufficient.
>
> please describe your actual problem in detail and how this actually fixes
> things for you.
> -mike
>
>
I agree with Mike's reply i.e. -g flag provides sufficient debug
information.
But some debugger requires debug information in specific format i.e.
-gdwarf-2
For example Freescale CodeWarrior Debugger
Regards,
Prabhakar
>
>>
>>
>> On 04/25/2012 09:41 AM, Prabhakar Kushwaha wrote:
>>> Hi,
>>>
>>> This patch has review-pending from a very long time.
>>>
>>> I request the "mailing-list" to review this patch.
>>>
>>> Regards,
>>> Prabhakar
>>>
>>> On Wednesday 15 February 2012 02:25 PM, Prabhakar Kushwaha wrote:
>>>> Built u-boot elf file does not contain any dwarf informations by
>>>> default. This
>>>> information is required for debugging.
>>>>
>>>> Add dwarf ver 2 flag in DBGFLAGS.
>>>>
>>>> Signed-off-by: Radu Lazarescu<radu.lazarescu@freescale.com>
>>>> Signed-off-by: Prabhakar Kushwaha<prabhakar@freescale.com>
>>>> ---
>>>> Applies on http://git.denx.de/u-boot.git branch master
>>>>
>>>> config.mk | 2 +-
>>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>>
>>>> diff --git a/config.mk b/config.mk
>>>> index ddaa477..11bc20d 100644
>>>> --- a/config.mk
>>>> +++ b/config.mk
>>>> @@ -178,7 +178,7 @@ endif
>>>> # who are porting old code to latest mainline but not updating
>>>> $(AR).
>>>> ARFLAGS = $(error update your Makefile to use cmd_link_o_target
>>>> and not AR)
>>>> RELFLAGS= $(PLATFORM_RELFLAGS)
>>>> -DBGFLAGS= -g # -DDEBUG
>>>> +DBGFLAGS= -g -gdwarf-2 # -DDEBUG
>>>> OPTFLAGS= -Os #-fomit-frame-pointer
>>>>
>>>> OBJCFLAGS += --gap-fill=0xff
>>>
>>>
>>>
>>> _______________________________________________
>>> U-Boot mailing list
>>> U-Boot at lists.denx.de
>>> http://lists.denx.de/mailman/listinfo/u-boot
>>>
>>
>>
>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
>
>
next prev parent reply other threads:[~2012-06-19 5:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 8:55 [U-Boot] [PATCH] config.mk:Update DBGFLAGS with dwarf information Prabhakar Kushwaha
2012-04-25 4:11 ` Prabhakar Kushwaha
2012-05-24 4:43 ` Prabhakar Kushwaha
2012-05-24 4:47 ` Graeme Russ
[not found] ` <4FE00741.4040202@freescale.com>
2012-06-19 5:08 ` Prabhakar Kushwaha [this message]
2012-06-25 4:57 ` Prabhakar Kushwaha
2012-06-25 5:03 ` Graeme Russ
2012-06-25 7:21 ` Wolfgang Denk
2012-06-25 7:40 ` Prabhakar Kushwaha
2012-05-14 5:53 ` Mike Frysinger
2012-10-15 23:13 ` [U-Boot] " Tom Rini
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=4FE00969.5070405@freescale.com \
--to=prabhakar@freescale.com \
--cc=u-boot@lists.denx.de \
/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