Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagercon.com>
To: anocean@aromasoft.com
Cc: gdb@sources.redhat.com
Subject: Re: gdb supports dwarf2 which is generated by ADS compiler?
Date: Wed, 07 Jan 2004 17:15:00 -0000	[thread overview]
Message-ID: <3FFC3EAC.8000506@eagercon.com> (raw)
In-Reply-To: <000701c3d4ec$f8c1d9d0$0e01a8c0@bathory>

Jang, Jaewoo wrote:
> I try to debug elf dwarf2 format whcih is generated by ADS 1.0.1 compiler.
> It seems that gdb support dwarf2 spec.
> But ARM dwarf2 spec is somehow modified from drawf2 spec.
> This is the reference of ARM dwar2 spec.
> http://www.linuxbase.org/spec/refspecs/dwarf/ARMDwarf2.pdf

The ARM document specifies how their compiler generates DWARF.
They describe the choices which they make, as well as the very minor
areas in which they diverge from the DWARF 2 standard.

> I want to know whether gdb will support ARM dwarf2 format,
> or it is possible to patch gdb that support ARM dwarf format.

There is no ARM DWARF 2 format, as such.  DWARF is permissive --
it allows compilers to generate more or less information.  The
ARM document does what few other compilers do: explain what choices
they made and their rationale.

On the other hand, if a compiler generates DWARF which diverges
from the standard, one has to expect that a debugger will have
trouble interpreting it.  I don't think that ADS does this.

If you have a specific question (i.e., "does gdb support this particular
output from ADS?" or "is this particular DWARF generated by ADS correct?"),
then you will more likely get a more specific response.

> Now I try to understand source codes that is part of reading elf format.
> It is hard to understand. :(
> 
> please help me.
> 
> Sorry for my bad writing.
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Let's get rock.
> +82 (2) 3284-2463 anocean@aromasoft.com
> 


-- 
Michael Eager	 Eager Consulting     eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077


  reply	other threads:[~2004-01-07 17:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07  7:07 Jang, Jaewoo
2004-01-07 17:15 ` Michael Eager [this message]
2004-01-08  4:06   ` Jang, Jaewoo
2004-01-08 13:12     ` Jang, Jaewoo
2004-01-08 14:10       ` Daniel Jacobowitz
2004-01-09 14:30         ` Jang, Jaewoo
2004-01-08 14:10       ` Tim Combs
2004-01-08 14:12         ` Daniel Jacobowitz
2004-01-08 23:46 ` Jim Blandy
2004-01-09 17:16   ` Michael Eager
2004-01-09 22:30     ` Tim Combs

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=3FFC3EAC.8000506@eagercon.com \
    --to=eager@eagercon.com \
    --cc=anocean@aromasoft.com \
    --cc=gdb@sources.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