From: "Jang, Jaewoo" <jaewoo.jang@aromasoft.com>
To: "'Daniel Jacobowitz'" <drow@mvista.com>
Cc: <gdb@sources.redhat.com>
Subject: RE: gdb supports dwarf2 which is generated by ADS compiler?
Date: Fri, 09 Jan 2004 14:30:00 -0000 [thread overview]
Message-ID: <000001c3d6bd$171faa20$f617203d@bathory> (raw)
In-Reply-To: <20040108141039.GA16913@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]
I am enclosing sample file.
The files in the zipped file are source code, and compiled executables.
"gcc.client" is compiled by GCC 3.2.1, and "ads.client" is compiled by ADS
1.0.1. I am using gdb version 6.0. The problem is arm-elf-gdb can not
disassamble ads.client correctly. There are some problem on checking ARM
mode and THUMB mode. I think that the problem is derived from reading dwarf2
format.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Let's get rock.
+82 (2) 3284-2463 anocean@aromasoft.com
> -----Original Message-----
> From: Daniel Jacobowitz [mailto:drow@mvista.com]
> Sent: Thursday, January 08, 2004 11:11 PM
> To: anocean@aromasoft.com
> Cc: 'Michael Eager'; gdb@sources.redhat.com
> Subject: Re: gdb supports dwarf2 which is generated by ADS compiler?
>
>
> On Thu, Jan 08, 2004 at 10:12:28PM +0900, Jang, Jaewoo wrote:
> >
> > I am concerned for not reading my words because they are
> below replys.
> >
> > I wrote as
> >
> > As Trace32 debugger can also read the elf file which is generated
> > by ADS, I think the elf file is not far from DWARF spec.
> >
> > But ADS debugger(adw) can not read gdb's elf file.
> > I am curious that gdb can support DWARF spec correctly.
> >
> > Anyway, I just have one question.
> > does gdb support this particular output from ADS?
> > (I don't think DWARF generated by ADS is not correct.)
>
> How could we tell? You didn't provide a sample, a dump, or
> any information about "this particular output".
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
>
[-- Attachment #2: sample.tgz --]
[-- Type: application/x-compressed, Size: 4204 bytes --]
next prev parent reply other threads:[~2004-01-09 14:30 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
2004-01-08 4:06 ` Jang, Jaewoo
2004-01-08 13:12 ` Jang, Jaewoo
2004-01-08 14:10 ` Tim Combs
2004-01-08 14:12 ` Daniel Jacobowitz
2004-01-08 14:10 ` Daniel Jacobowitz
2004-01-09 14:30 ` Jang, Jaewoo [this message]
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='000001c3d6bd$171faa20$f617203d@bathory' \
--to=jaewoo.jang@aromasoft.com \
--cc=anocean@aromasoft.com \
--cc=drow@mvista.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