Changeset f28dfb36 in rtems for doc/FAQ/debug.t


Ignore:
Timestamp:
Jul 28, 1999, 5:29:54 PM (21 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
f94e76ba
Parents:
f82c98b
Message:

Added information on using objcopy to produce IEEE-695 format.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/FAQ/debug.t

    rf82c98b rf28dfb36  
    4747In this case, the first block on the C Heap has 8,058,280 bytes left.
    4848
     49@section How do I convert an executable to IEEE-695?
    4950
     51This section is based on an email from Andrew Bythell
     52<abythell@@nortelnetworks.com> in July 1999.
     53
     54Using Objcopy to convert m68k-coff to IEEE did not work.  The new IEEE
     55object could not be read by tools like the XRay BDM Debugger. 
     56
     57The exact nature of this problem is beyond me, but I did narrow it down to a
     58problem with objcopy in binutils 2-9.1.  To no surprise, others have
     59discovered this problem as well, as it has been fixed in later releases.
     60
     61I compiled a snapshot of the development sources from 07/26/99 and
     62everything now works as it should.  The development sources are at
     63http://sourceware.cygnus.com/binutils  (thanks Ian!)
     64
     65Additional notes on converting an m68k-coff object for use with XRay (and
     66others):
     67
     68@enumerate
     69
     70
     71@item The m68k-coff object must be built with the -gstabs+ flag.  The -g flag
     72alone didn't work for me. 
     73
     74@item Run Objcopy with the --debugging flag to copy debugging information.
     75
     76@end enumerate
     77
     78
Note: See TracChangeset for help on using the changeset viewer.