From: Daniel Jacobowitz <drow@mvista.com>
To: Richard.Earnshaw@arm.com
Cc: Kevin Squail Endres <kevine@wildseed.com>, gdb@sources.redhat.com
Subject: Re: cross targeted gdb and corefiles
Date: Thu, 16 May 2002 11:07:00 -0000 [thread overview]
Message-ID: <20020516174200.GA16866@nevyn.them.org> (raw)
In-Reply-To: <200205161724.SAA21124@cam-mail2.cambridge.arm.com>
On Thu, May 16, 2002 at 06:24:53PM +0100, Richard Earnshaw wrote:
> > I am using a gdb built from a cvs snapshot from 4-29 that is i386 hosted and
> > ARM targeted.
> >
> > this gdb does not support reading arm cores. I would like to get a backtrace
> > for an arm failure (indeterminant - cannot set a breakpoint) without running
> > an arm native gdb (or running my application under gdbserver). Is that
> > possible??
>
> Not at present.
>
> >
> > if not - is it a feature slated to be added to cross targeted gdb soon? I
> > know i run my application under gdbserver...
>
> Maybe. Some targets can now do this. Precisely which target OS are you
> using?
He's on GNU/Linux, IIRC...
Doing cross coredumps is trivial; I put all the BFD machinery in place
for a number of GNU/Linux targets, and others did it for the various
BSDs. I'd post my ARM patches for this but I doubt even a line of them
applies any more after your extensive ARM cleanups.
The only thing you have to do is move supply_gregset and
supply_fpregset to the tdep file, and then link in corelow/core-regset
as target instead of nat objects. This means a little bit of grubbing
about in target header files to copy out definitions for regsets, but
only a little.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-16 18:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 10:10 Kevin "Squail" Endres
2002-05-16 10:25 ` Richard Earnshaw
2002-05-16 11:07 ` Daniel Jacobowitz [this message]
2002-05-16 10:28 Kevin "Squail" Endres
2002-05-16 11:35 Kevin "Squail" Endres
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 15:28 Kevin "Squail" Endres
2002-05-16 15:33 ` Kevin Buettner
2002-05-16 15:43 Kevin "Squail" Endres
2002-05-16 15:53 ` Kevin Buettner
2002-05-16 15:55 Kevin "Squail" Endres
2002-05-16 15:56 Kevin "Squail" Endres
2002-05-16 16:05 Kevin "Squail" Endres
2002-05-16 16:17 ` Kevin Buettner
2002-05-16 16:28 Kevin "Squail" Endres
2002-05-17 8:06 ` Daniel Jacobowitz
2002-05-16 17:18 Kevin "Squail" Endres
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=20020516174200.GA16866@nevyn.them.org \
--to=drow@mvista.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb@sources.redhat.com \
--cc=kevine@wildseed.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