From: "Kevin \"Squail\" Endres" <kevine@wildseed.com>
To: 'Kevin Buettner' <kevinb@redhat.com>,
"Kevin \"Squail\" Endres" <kevine@wildseed.com>,
'Daniel Jacobowitz' <drow@mvista.com>,
Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com
Subject: RE: cross targeted gdb and corefiles
Date: Thu, 16 May 2002 15:28:00 -0000 [thread overview]
Message-ID: <43CB1396676FD4119F03001083FD2994F5F224@neptune.kirkland.local> (raw)
Yep had just figured out to move the supply_* (and the nwfpe*) functions
from arm-linux-nat.c to arm-linux-tdep.c. I did assume that the kernel
headers needed to be from an arm configured kernel so i set the prefix to
the root of my cross toolchain whemn i configured.
everything builds but when i try to read an arm core i get a warning about
the size of the gregset struct in the core (so possibly i am truly not
including the correct headers??)
trying a few more things...
sany help is GREATLY appreciated....
:]k
-----Original Message-----
From: Kevin Buettner [mailto:kevinb@redhat.com]
Sent: Thursday, May 16, 2002 3:24 PM
To: Kevin "Squail" Endres; 'Daniel Jacobowitz'; Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com
Subject: Re: cross targeted gdb and corefiles
On May 16, 3:01pm, Kevin \Squail\ Endres wrote:
> i moved the supply_* functions from i386-nat (only ones i could find in
the
> gdb source)to arm-linux-tdep.c.
> (given that there is no fp on arm - is the supply_fpregset really
> necessary???)
I haven't been following this closely, but I think you need to move the
supply_* functions from the arm version of the nat.c file to the arm
tdep.c file.
You have to make sure that there aren't any host dependencies though.
I.e, you can't make use of system header files.
Kevin
next reply other threads:[~2002-05-16 22:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 15:28 Kevin "Squail" Endres [this message]
2002-05-16 15:33 ` Kevin Buettner
-- strict thread matches above, loose matches on Subject: below --
2002-05-16 17:18 Kevin "Squail" Endres
2002-05-16 16:28 Kevin "Squail" Endres
2002-05-17 8:06 ` Daniel Jacobowitz
2002-05-16 16:05 Kevin "Squail" Endres
2002-05-16 16:17 ` Kevin Buettner
2002-05-16 15:56 Kevin "Squail" Endres
2002-05-16 15:55 Kevin "Squail" Endres
2002-05-16 15:43 Kevin "Squail" Endres
2002-05-16 15:53 ` Kevin Buettner
2002-05-16 15:01 Kevin "Squail" Endres
2002-05-16 15:23 ` Kevin Buettner
2002-05-16 16:18 ` Jason R Thorpe
2002-05-17 8:20 ` Richard Earnshaw
2002-05-16 11:35 Kevin "Squail" Endres
2002-05-16 10:28 Kevin "Squail" Endres
2002-05-16 10:10 Kevin "Squail" Endres
2002-05-16 10:25 ` Richard Earnshaw
2002-05-16 11:07 ` Daniel Jacobowitz
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=43CB1396676FD4119F03001083FD2994F5F224@neptune.kirkland.local \
--to=kevine@wildseed.com \
--cc=Richard.Earnshaw@arm.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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