public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: John Groves <John@Groves.net>
Cc: gdb@sources.redhat.com
Subject: Re: Cross-platform gdb/kgdb
Date: Tue, 25 Mar 2003 16:35:00 -0000	[thread overview]
Message-ID: <20030325163453.GA16179@nevyn.them.org> (raw)
In-Reply-To: <3E7F7B94.2040104@Groves.net>

On Mon, Mar 24, 2003 at 03:41:40PM -0600, John Groves wrote:
> I'm hoping someone can point me in the right direction...or tell me it 
> ain't worth trying...
> 
> I need to do some kernel debugging with an HP IA-64 system (hpux), and 
> it's the only hpux box available.  It would be cool to compile a 
> linux-resident gdb that would run as the kgdb control system for the 
> IA-64 hpux target.
> 
> FYI (you may know) hp maintains "kwdb" which is gdb/kgdb for hpux, so I 
> have the code for the target system. But hp hasn't tried cross-platform.
> 
> Q: Are the sources in the gdb build tree organized such that I can make 
> the target system include files available without them getting mixed up 
> with the host system includes?
> 
> Having run "./configure  --host=i386-unknown-linux --target=ia64-hp", I 
> note that files in the gdb directory need access to *target* system 
> include files; but I also see plenty of sources in that directory that 
> include stuff that should probably be local (fcntl, curses, stuff like 
> that).
> 
> Q: If it's not completely futile, where could I look for an example or 
> any helpful info?

It should work; however, I do not know whether ia64-hpux is supported. 
A cross debugger should _not_ need any headers from the target system
to build.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

      reply	other threads:[~2003-03-25 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 21:41 John Groves
2003-03-25 16:35 ` Daniel Jacobowitz [this message]

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=20030325163453.GA16179@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=John@Groves.net \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).