public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michael Schwingen <rincewind@discworld.dascon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] Adds general Freescale external debugger support
Date: Sun, 30 Jan 2011 23:50:05 +0100	[thread overview]
Message-ID: <4D45EB1D.4020104@discworld.dascon.de> (raw)
In-Reply-To: <20110130194307.58FA4CD1385@gemini.denx.de>

Am 01/30/2011 08:43 PM, schrieb Wolfgang Denk:
>
> I don't see where this is specific to the Power architecture either -
> expect that you only tested it there.
>
> My understanding is that you enable debug settings for the GNU
> debugger.
>
> Do these need to be architecture specific? Probably not.
I do remember that we needed architecture-dependent debug options on a
system I worked on in the past, because the preferred debug format was
different on different platforms (all using gcc/binutils/gdb).

> Do these need to be enabled by a new #define?  What would be the
> disadvantages of having these options always enabled, for all
> architectures?
Always having debug info in the ELF file should not cause problems IMHO,
and one set of settings per platform should be enough.

cu
Michael

  reply	other threads:[~2011-01-30 22:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30  9:58 [U-Boot] [PATCH v2] Adds general Freescale external debugger support Roy Zang
2011-01-30 19:43 ` Wolfgang Denk
2011-01-30 22:50   ` Michael Schwingen [this message]
2011-01-31 10:43     ` Wolfgang Denk
2011-01-31 11:17       ` Michael Schwingen
2011-03-07  7:24         ` Zang Roy-R61911
2011-03-07  7:18     ` Zang Roy-R61911
2011-03-07 19:05       ` Scott Wood

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=4D45EB1D.4020104@discworld.dascon.de \
    --to=rincewind@discworld.dascon.de \
    --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