Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Hiro Sugawara <hsugawar@brocade.com>
To: "'more'" <morezeng@certaingroup.com>
Cc: gdb@sources.redhat.com
Subject: RE: linux core support
Date: Tue, 26 Jun 2001 10:23:00 -0000	[thread overview]
Message-ID: <F13508319A1CD41187DE00508BACED6A02067390@cs2ex.brocade.com> (raw)

> -----Original Message-----
> From: more [ mailto:morezeng@certaingroup.com ]
> Sent: Monday, June 25, 2001 20:35
> To: Hiro Sugawara
> Subject: Re: linux core support
> 
> 
> Very thanks for your reply, it seems I should modify some 
> code to make the 
> cross core file supported. But I am not very clear of the 
> inner mechanism, 
> the blow is my curious problem.
> 
> > When I ported GDB for SunOS-to-PowerPC, I found two tricks 
> were needed to
> > make the cross GDB support core files:
> > 1) Shuffle Makefile fragments (*.mh and *.mt) so that core 
> file support is
> >    included;
> In these fragments, there are some objfiles registering, you 
> mean I should 
> provide my own cross core file supporting file and register 
> it in *.mh and 
> *.mt?

If the native build already has all the necessary files, reshuffling
is good enough; otherwise, you may have to provide your own.

> > 2) Modify Makefile to use the target's <sys/procfs.h> and 
> other related
> > files
> >    to compile bfd/elf.c.
> You mean I should read some document concerning elf and core 
> file format, 
> have you any suggestion?

For ELF and other file formats, check
http://developer.intel.com/vtune/tis.htm .

hiro


             reply	other threads:[~2001-06-26 10:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26 10:23 Hiro Sugawara [this message]
2001-06-26 19:12 ` more
  -- strict thread matches above, loose matches on Subject: below --
2001-06-23 22:51 more
2001-06-24  3:15 ` Daniel Jacobowitz
2001-06-24  4:52   ` more

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=F13508319A1CD41187DE00508BACED6A02067390@cs2ex.brocade.com \
    --to=hsugawar@brocade.com \
    --cc=gdb@sources.redhat.com \
    --cc=morezeng@certaingroup.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