public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Philp <andrew.philip@trintech.com>
To: jtc@redback.com
Cc: gdb@sourceware.cygnus.com, tm@netcom.com
Subject: GDB with Hitachi Linker output
Date: Thu, 12 Oct 2000 11:14:00 -0000	[thread overview]
Message-ID: <F4F6A84AB884D31198F20008C724FD4A024C3A92@ntdub0e.trintech.com> (raw)

Hello,
with regard to your earlier email correspondence which I found at
redhat.com, could you please update me as to what the latest is regarding
using GDB and Hitachi linker output. I'm successfully remote debugging a H8
target and just need to load the symbol table to get source level debugging
working.

I've been looking for a object file converter utility, which out much luck.

thanks for helping
Andrew


>> original email trail.........
The SRCONV utility is actually pretty broken, through no fault of Cygnus.We
ran into the problem three years ago that SRCONV-emitted files caused the
Hitachi in-circuit emulator to crash. After much consultation with both
sides, we determined that:1) The Hitachi SYSROF spec only describes the
output of the data from the compiler/linker, and do not specify implicit
ordering dependencies, and 2) linker/debugger are fragile and do not emit
proper error messages when a certain section is out of order.Therefore, it
was impossible to debug the problem and we gave up on SRCONV.Toshi> > >>>>>
"Bill" == Bill Gatliff <gatliff@haulpak.com> writes:> Bill> Is anyone using
GDB sh-hitachi-hms with executables supplied by> Bill> the Hitachi linker?>
> I don't think so. > > AFAIK, the hitachi object format is sysroff. There
is a sysroff to> COFF converter in binutils (srconv), but nothing to do the
reverse. I> vaguely remember a receiving email from Ian Taylor two or three
years> ago that said that support for whatever was missing in BFD that
caused> srconv to be a separate program (instead of available through
objcopy)> had been added. That project never became high enough priority to>
follow up. > > It's possible that the email was referring to nlmconv instead
of> srconv, since I worked on both programs in that time frame. I'm > sorry
I can't remember any more details.> > --jtc> > -- > J.T. Conklin> RedBack
Networks> 

Andrew Philp

Trintech Group Plc,
Trintech Building,
South County Business Park
Leopardstown,
Dublin 18.
Phone: +353 1 207 4283

This email should be considered personal
and does not necessarily reflect the views 
of Trintech or any other of its employees
or officers.

                 reply	other threads:[~2000-10-12 11:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=F4F6A84AB884D31198F20008C724FD4A024C3A92@ntdub0e.trintech.com \
    --to=andrew.philip@trintech.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=jtc@redback.com \
    --cc=tm@netcom.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).