From: Fernando Nasser <fnasser@cygnus.com>
To: ee96162@ee.iitm.ernet.in
Cc: gdb@sourceware.cygnus.com
Subject: Re: ARM TARGET
Date: Fri, 26 May 2000 10:05:00 -0000 [thread overview]
Message-ID: <392EAED8.15A14708@cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10005262201320.5023-100000@volt.ee.iitm.ernet.in>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4831 bytes --]
Lavu Sridhar wrote:
>
> I have the file gdb 5.0 . I had to make changes in the gdb/makefile to
> enable the target rdi debugging.
>
You should not change anything. Use the original gdb 5 tar file.
No changes are necessary to debug Angel targets.
But this is irrelevant (see below).
> When I had done ./configure in the main directory, it was configuring gdb
> for host i686 and target also i686, where as I want the target to be my
> Cirrus Logic Arm 7500FE Baord. I do not know how to sepcify the exact
> option for this arm processor. Currently the board has only the ANGEL
> debugger program running.
>
Again you did not send me the configure command that you used.
However, it is clear from your description that you did not read the instructions
on how to build it. Please do so before asking for help on the net groups/lists.
(Read the FAQs as well when they exist).
Your configure line will need a --target=arm-elf or a --target=arm-coff
for the kind of board you have.
But, again, it won't do what you need...
> I already have the vmlinux, and the zImage files for the Linxu kernel
> 2.3.99 . My host PC is RedHat 6.1 and i686 architecture.
>
> I am using the gdb mainly for downloading the image files into the RAM on
> my target baord from my Host PC.
>
You are definitively in the wrong track AND in the wrong list.
The zImage file is not in a format that gdb can understand.
vmlinus is (elf) but this is of no use to you.
I'd suggest you look at LILO (the arm version or arm equivalent of it) and
try to write some boot ROM code that either does what it does or loads it
from floppy or something.
But this is a topic for the ARM Linux mailing list.
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@cygnus.com
2323 Yonge Street, Suite #300 Tel: 416-482-2661 ext. 311
Toronto, Ontario M4P 2C9 Fax: 416-482-6299
From donnte@microsoft.com Fri May 26 10:30:00 2000
From: Donn Terry <donnte@microsoft.com>
To: Donn Terry <donnte@microsoft.com>, Mark Mitchell <mark@codesourcery.com>, rth@cygnus.com
Cc: kettenis@wins.uva.nl, Peter.Schauer@Regent.E-Technik.TU-Muenchen.DE, kingdon@redhat.com, gdb@sourceware.cygnus.com
Subject: RE: Suggested (easier) fix to ... RE: Regressions problem (200 failures)
Date: Fri, 26 May 2000 10:30:00 -0000
Message-id: <309F4FC4705DC844987051A517E9E39B09D1C2@red-pt-02.redmond.corp.microsoft.com>
X-SW-Source: 2000-05/msg00139.html
Content-length: 2262
Title: RE: Suggested (easier) fix to ... RE: Regressions problem (200 fa ilures)
And a
bit more... the rebuild/regression did succeed (after some
tweaking)
and
the problem with __main is in the current CVS as well.
Â
Donn
-----Original Message----- From: Donn Terry Sent:
Thursday, May 25, 2000 8:23 PM To: Mark Mitchell;
rth@cygnus.com Cc: kettenis@wins.uva.nl;
Peter.Schauer@Regent.E-Technik.TU-Muenchen.DE; kingdon@redhat.com;
gdb@sourceware.cygnus.com Subject: RE: Suggested (easier) fix to ...
RE: Regressions problem (200 failures)
Mark:
Â
I just tried to rebuild with my interim patch in place, and found that
RTH had completely
rewritten the area. If I don't run into too many ICEs during the
rebuild of the compiler
suite (it comes and goes regularly depending on who has patched what)
I'll know
something tomorrow (Fri) about what effect his changes had on this, but
from
 looking at the code, it may have the same problem. (I'm
skipping my patch for the moment.)
Â
Richard: quick synopsis: the code in this area doesn't (didn't?) take
into account the
possibility of there being a call to __main, with the consequence that
the initial
breakpoint for main ends up at the {, rather than at the first statement
*if* the
call to __main is generated.
Â
Donn
-----Original Message----- From: Mark Mitchell
Sent: Thu 5/25/2000 8:46 AM To: Donn Terry
Cc: kettenis@wins.uva.nl;
Peter.Schauer@Regent.E-Technik.TU-Muenchen.DE; kingdon@redhat.com;
gdb@sourceware.cygnus.com Subject: RE: Suggested (easier) fix to
... RE: Regressions problem (200 fa ilures)
>>>>> "Donn" == Donn Terry
<donnte@microsoft.com> writes:
   Donn> I can't answer why any better
than the author of the change   Â
Donn> that started all this ;-) .
Touche.
OK, now I understand the problem -- thanks to you.Â
I'll look back at why I did what I did -- and then
see if I can figure out how to fix it.
Thanks for bearing with me on this.
-- Mark
Mitchell                 Â
mark@codesourcery.com CodeSourcery,
LLCÂ Â Â Â Â Â Â Â Â Â Â Â Â Â
http://www.codesourcery.com
next parent reply other threads:[~2000-05-26 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10005262201320.5023-100000@volt.ee.iitm.ernet.in>
2000-05-26 10:05 ` Fernando Nasser [this message]
[not found] <Pine.LNX.4.10.10005262124280.3272-100000@volt.ee.iitm.ernet.in>
2000-05-26 9:27 ` Fernando Nasser
2000-05-26 8:23 Lavu Sridhar
2000-05-26 8:49 ` Fernando Nasser
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=392EAED8.15A14708@cygnus.com \
--to=fnasser@cygnus.com \
--cc=ee96162@ee.iitm.ernet.in \
--cc=gdb@sourceware.cygnus.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